Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36875c9b1376d09d1c129004019ff312501bc7d322d316dcfc309269a92d038b

Tx prefix hash: ae0b3d1e1c5a4a768d830f362b08171994fbabb714d9e07f6060c69ae92fbf42
Tx public key: e472f0c46baa4566e2e81ef9bc0007f97dad093cca8c4402d9e91b88f93d156e
Timestamp: 1720601242 Timestamp [UCT]: 2024-07-10 08:47:22 Age [y:d:h:m:s]: 00:196:04:19:25
Block: 1062549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140327 RingCT/type: yes/0
Extra: 01e472f0c46baa4566e2e81ef9bc0007f97dad093cca8c4402d9e91b88f93d156e02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 659e0330f2374820994751d5ad44a4c03e9df61808f79786eb0906456cf71370 0.600000000000 1533054 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": 1062559, "vin": [ { "gen": { "height": 1062549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "659e0330f2374820994751d5ad44a4c03e9df61808f79786eb0906456cf71370" } } ], "extra": [ 1, 228, 114, 240, 196, 107, 170, 69, 102, 226, 232, 30, 249, 188, 0, 7, 249, 125, 173, 9, 60, 202, 140, 68, 2, 217, 233, 27, 136, 249, 61, 21, 110, 2, 17, 0, 0, 0, 10, 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