Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c598c34084d0f303781925f41a2b2d88d7adc4194b260da4f78c14da1046f98a

Tx prefix hash: b72429064ee4f646e061eea2a1a11aebef783788ea74dfccfc3e093ea524748b
Tx public key: ed5f1f26565c11a85614a47675c6bce2ac4a7731e93557a1bf732ea482e2c853
Timestamp: 1704527901 Timestamp [UCT]: 2024-01-06 07:58:21 Age [y:d:h:m:s]: 01:153:12:30:10
Block: 929262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370890 RingCT/type: yes/0
Extra: 01ed5f1f26565c11a85614a47675c6bce2ac4a7731e93557a1bf732ea482e2c8530211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8556da76815eafce239afa71d81b9112c05773568a549e7330c518621d9c4d2 0.600000000000 1387132 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 929272, "vin": [ { "gen": { "height": 929262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8556da76815eafce239afa71d81b9112c05773568a549e7330c518621d9c4d2" } } ], "extra": [ 1, 237, 95, 31, 38, 86, 92, 17, 168, 86, 20, 164, 118, 117, 198, 188, 226, 172, 74, 119, 49, 233, 53, 87, 161, 191, 115, 46, 164, 130, 226, 200, 83, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8