Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95c95b4f0161aa41fd4e5c4e5cc0c76ebd694f13756861e5958fb16e29d64938

Tx prefix hash: d358a7e32ec8c7faeffd4bd60ec40b28f0fca8c80986d115a10811244bdf299e
Tx public key: 600c72c455251d711a6ef001a1c38b5ea8232c80795d7730fc46e30105211a8b
Timestamp: 1750880814 Timestamp [UCT]: 2025-06-25 19:46:54 Age [y:d:h:m:s]: 00:141:05:58:44
Block: 1312708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98917 RingCT/type: yes/0
Extra: 01600c72c455251d711a6ef001a1c38b5ea8232c80795d7730fc46e30105211a8b02110000002bbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 284226d5a8ceffb9f6457975e70b8837dc330d48c22fd5ba5cd9cba02eead579 0.600000000000 1800343 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": 1312718, "vin": [ { "gen": { "height": 1312708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "284226d5a8ceffb9f6457975e70b8837dc330d48c22fd5ba5cd9cba02eead579" } } ], "extra": [ 1, 96, 12, 114, 196, 85, 37, 29, 113, 26, 110, 240, 1, 161, 195, 139, 94, 168, 35, 44, 128, 121, 93, 119, 48, 252, 70, 227, 1, 5, 33, 26, 139, 2, 17, 0, 0, 0, 43, 191, 81, 178, 162, 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