Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 425d45b7031a679d6501b8b70a41dfef0421bcaf47b7cbe4c2012b8da0416dc7

Tx prefix hash: e611400bffbcb5c4efdd9984c135260e6634b12093149723348ad67df57e4d87
Tx public key: 83842950d95bf7b5fdee497b2a6e3e0eceb063aa1929e7149c13d77a3a21d074
Timestamp: 1711798995 Timestamp [UCT]: 2024-03-30 11:43:15 Age [y:d:h:m:s]: 00:351:15:19:57
Block: 989586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251393 RingCT/type: yes/0
Extra: 0183842950d95bf7b5fdee497b2a6e3e0eceb063aa1929e7149c13d77a3a21d0740211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0863b0d5a80f510c75e74e1609b930990dfb5966934154650ea5e46b4de78a89 0.600000000000 1449885 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": 989596, "vin": [ { "gen": { "height": 989586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0863b0d5a80f510c75e74e1609b930990dfb5966934154650ea5e46b4de78a89" } } ], "extra": [ 1, 131, 132, 41, 80, 217, 91, 247, 181, 253, 238, 73, 123, 42, 110, 62, 14, 206, 176, 99, 170, 25, 41, 231, 20, 156, 19, 215, 122, 58, 33, 208, 116, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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