Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f4899e29634e548509aae02c68f6b455cd233535f59f9ddcfd3c802a1c7e87b

Tx prefix hash: ed15f9438e5e23bd5b2a083fc24d803ea64a65a6978a32feae9e13747fc86534
Tx public key: 1efc60b1d92a9538a92d776d97fe102a3c65abd61591b9b2808dd296058f79aa
Timestamp: 1751548769 Timestamp [UCT]: 2025-07-03 13:19:29 Age [y:d:h:m:s]: 00:185:02:41:37
Block: 1317962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130619 RingCT/type: yes/0
Extra: 011efc60b1d92a9538a92d776d97fe102a3c65abd61591b9b2808dd296058f79aa0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beae1ed2b786444de002e407904c4a2600661bb73f4c65a535864ad31a5eb310 0.600000000000 1805633 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": 1317972, "vin": [ { "gen": { "height": 1317962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beae1ed2b786444de002e407904c4a2600661bb73f4c65a535864ad31a5eb310" } } ], "extra": [ 1, 30, 252, 96, 177, 217, 42, 149, 56, 169, 45, 119, 109, 151, 254, 16, 42, 60, 101, 171, 214, 21, 145, 185, 178, 128, 141, 210, 150, 5, 143, 121, 170, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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