Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9b839b16b7db5e388a4046fdc2ccfb4acb562d3e4bd8deafc14d5aabaacc14f

Tx prefix hash: be0901c5c2965b9fc632463c99d68673635e0c686e342d3c988f8c404303f7da
Tx public key: 0dd48d14f32308d5e8feba90517133dce7a9d78a8d4b55a8175a2e2c49aeb1de
Timestamp: 1754709173 Timestamp [UCT]: 2025-08-09 03:12:53 Age [y:d:h:m:s]: 00:104:22:50:34
Block: 1343219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74131 RingCT/type: yes/0
Extra: 010dd48d14f32308d5e8feba90517133dce7a9d78a8d4b55a8175a2e2c49aeb1de0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 131b0d23bc898b727a527ed7901de46b2a9125da0cac72ce0d4f1dbab4bb1a0b 0.600000000000 1831058 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": 1343229, "vin": [ { "gen": { "height": 1343219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "131b0d23bc898b727a527ed7901de46b2a9125da0cac72ce0d4f1dbab4bb1a0b" } } ], "extra": [ 1, 13, 212, 141, 20, 243, 35, 8, 213, 232, 254, 186, 144, 81, 113, 51, 220, 231, 169, 215, 138, 141, 75, 85, 168, 23, 90, 46, 44, 73, 174, 177, 222, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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