Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58f14f352c0d5e2ceb43223109be3a7c41d636bf89fc8065fb132a4de0c88cd8

Tx prefix hash: f54b4f38c0b219f97d96bdf99ba7d54ea0bdcd0c829f5dec090fd1af2d186cce
Tx public key: a29b8dc6ca06bb906f3f906e60d030e123d115e5f5edc3bc1fd4364d713edeba
Timestamp: 1720906143 Timestamp [UCT]: 2024-07-13 21:29:03 Age [y:d:h:m:s]: 00:249:00:42:34
Block: 1065076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177919 RingCT/type: yes/0
Extra: 01a29b8dc6ca06bb906f3f906e60d030e123d115e5f5edc3bc1fd4364d713edeba02110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6a84a13cf30acd4674cba3d5e20fd9aa9f2a4c4687f34cce61fa48133d9755f 0.600000000000 1535619 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": 1065086, "vin": [ { "gen": { "height": 1065076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6a84a13cf30acd4674cba3d5e20fd9aa9f2a4c4687f34cce61fa48133d9755f" } } ], "extra": [ 1, 162, 155, 141, 198, 202, 6, 187, 144, 111, 63, 144, 110, 96, 208, 48, 225, 35, 209, 21, 229, 245, 237, 195, 188, 31, 212, 54, 77, 113, 62, 222, 186, 2, 17, 0, 0, 0, 15, 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