Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d96e2864b740671d11091d762aff723307c2353745485bcd1035cfd418dc7bd4

Tx prefix hash: 30a399f05d2b3cc914c4e9eefff4635385cdb6c9c451e9bec98995ba2b99d413
Tx public key: db1fd596c3d50d11e0d6121c6e32bd712e4432a5fe04273c754767838d40bc1f
Timestamp: 1727724752 Timestamp [UCT]: 2024-09-30 19:32:32 Age [y:d:h:m:s]: 01:059:05:09:41
Block: 1121600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300734 RingCT/type: yes/0
Extra: 01db1fd596c3d50d11e0d6121c6e32bd712e4432a5fe04273c754767838d40bc1f02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40aa931e5f08a76d3fec939d2f6f18842aff82e47943fbbdce5643a117f2f308 0.600000000000 1603899 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": 1121610, "vin": [ { "gen": { "height": 1121600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40aa931e5f08a76d3fec939d2f6f18842aff82e47943fbbdce5643a117f2f308" } } ], "extra": [ 1, 219, 31, 213, 150, 195, 213, 13, 17, 224, 214, 18, 28, 110, 50, 189, 113, 46, 68, 50, 165, 254, 4, 39, 60, 117, 71, 103, 131, 141, 64, 188, 31, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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