Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cb420a9eb109d4a8fcc99ce335c38fdf1f408424d724eca6746c674a0162151

Tx prefix hash: 3614c91c2c8a3ace53e3b2c3b8c4a6caaa7091a9ebd566c8acc2606ed9e4cad4
Tx public key: e2b74ee6a52e243dd032739f80b3b05da46873eba1dba5560a7da2013552d790
Timestamp: 1721778815 Timestamp [UCT]: 2024-07-23 23:53:35 Age [y:d:h:m:s]: 01:132:15:26:07
Block: 1072295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353358 RingCT/type: yes/0
Extra: 01e2b74ee6a52e243dd032739f80b3b05da46873eba1dba5560a7da2013552d79002110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1dbb690b7d042c10d79acb8c8c3d897184e2518488a6a47d6bb42bb2ee473d7 0.600000000000 1544756 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": 1072305, "vin": [ { "gen": { "height": 1072295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1dbb690b7d042c10d79acb8c8c3d897184e2518488a6a47d6bb42bb2ee473d7" } } ], "extra": [ 1, 226, 183, 78, 230, 165, 46, 36, 61, 208, 50, 115, 159, 128, 179, 176, 93, 164, 104, 115, 235, 161, 219, 165, 86, 10, 125, 162, 1, 53, 82, 215, 144, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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