Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee229336862f87e2f697431b7a4cd64b4aaf5b6c4b154b7cf091f83f32e88778

Tx prefix hash: 1b84d63d9c1534c44c8119567bf2d2f68ac1c4bef554cda99f19203769456664
Tx public key: 80d7b4e6f9d44e3499310d66030bf53adfea6257c6a4399cf25a2a74be9b50fc
Timestamp: 1758832075 Timestamp [UCT]: 2025-09-25 20:27:55 Age [y:d:h:m:s]: 00:056:21:21:47
Block: 1376384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40720 RingCT/type: yes/0
Extra: 0180d7b4e6f9d44e3499310d66030bf53adfea6257c6a4399cf25a2a74be9b50fc02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 914ab0924fa33c43afb6e84e2e520d7e04b274071f804c2064ea911ba0c0bee9 0.600000000000 1864475 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": 1376394, "vin": [ { "gen": { "height": 1376384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "914ab0924fa33c43afb6e84e2e520d7e04b274071f804c2064ea911ba0c0bee9" } } ], "extra": [ 1, 128, 215, 180, 230, 249, 212, 78, 52, 153, 49, 13, 102, 3, 11, 245, 58, 223, 234, 98, 87, 198, 164, 57, 156, 242, 90, 42, 116, 190, 155, 80, 252, 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