Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9956aa1d1386aa920eafb44712f94097eeb8da5fad44b855bf928f053a5cc1c8

Tx prefix hash: 7c16f022725b3623302d6c286db3d2f5eff437a09543ce43d7f4ad5ccf394d19
Tx public key: 019dc7b2c9b64b8be0b0ff761130420ee1658eb21e469cf138a22a4f954a083e
Timestamp: 1759574616 Timestamp [UCT]: 2025-10-04 10:43:36 Age [y:d:h:m:s]: 00:080:12:11:15
Block: 1382530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57634 RingCT/type: yes/0
Extra: 01019dc7b2c9b64b8be0b0ff761130420ee1658eb21e469cf138a22a4f954a083e02110000000397baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d2429a30ea55cfc18b672f38d5644932d488c1945da4d8670a64b85b140fda5 0.600000000000 1870665 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": 1382540, "vin": [ { "gen": { "height": 1382530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d2429a30ea55cfc18b672f38d5644932d488c1945da4d8670a64b85b140fda5" } } ], "extra": [ 1, 1, 157, 199, 178, 201, 182, 75, 139, 224, 176, 255, 118, 17, 48, 66, 14, 225, 101, 142, 178, 30, 70, 156, 241, 56, 162, 42, 79, 149, 74, 8, 62, 2, 17, 0, 0, 0, 3, 151, 186, 249, 34, 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