Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69697780a843adf149355500594e6d0e1fcb53a7d5bc903c6edf1b515df89dc5

Tx prefix hash: d33ab6beae0fd566c03cb14bc690a6649fe82b8a2ecb1be4514be9a9ebf4bed0
Tx public key: 9023cfd5465c7255753664f6f40d076e5152975c80dde5e0dc80afea05f6b2d6
Timestamp: 1749499095 Timestamp [UCT]: 2025-06-09 19:58:15 Age [y:d:h:m:s]: 00:157:08:47:43
Block: 1301567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110145 RingCT/type: yes/0
Extra: 019023cfd5465c7255753664f6f40d076e5152975c80dde5e0dc80afea05f6b2d602110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9246f13fc9113c0b4151378abc4f571c595992bd139fb09af84b8b71c7008891 0.600000000000 1789126 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": 1301577, "vin": [ { "gen": { "height": 1301567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9246f13fc9113c0b4151378abc4f571c595992bd139fb09af84b8b71c7008891" } } ], "extra": [ 1, 144, 35, 207, 213, 70, 92, 114, 85, 117, 54, 100, 246, 244, 13, 7, 110, 81, 82, 151, 92, 128, 221, 229, 224, 220, 128, 175, 234, 5, 246, 178, 214, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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