Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7346d63c681fabf94de2c0e171cbd2dbf511c5fdc073a1c0484f0ab98c6c3c06

Tx prefix hash: 0d7f3140494f41753cb8444de90ce622b68be290ed9d65e7e07826cb97032e9a
Tx public key: ded142eb29ef08856ea05b9be69754593d2c8136aca8b6a48fa80b73c9247900
Timestamp: 1736117018 Timestamp [UCT]: 2025-01-05 22:43:38 Age [y:d:h:m:s]: 00:074:18:52:39
Block: 1191042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53226 RingCT/type: yes/0
Extra: 01ded142eb29ef08856ea05b9be69754593d2c8136aca8b6a48fa80b73c924790002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1807f83b0b0aa71509b8abd8b2672602a431b8ccf3c6dcadbdf3baec6eb2174 0.600000000000 1677565 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": 1191052, "vin": [ { "gen": { "height": 1191042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1807f83b0b0aa71509b8abd8b2672602a431b8ccf3c6dcadbdf3baec6eb2174" } } ], "extra": [ 1, 222, 209, 66, 235, 41, 239, 8, 133, 110, 160, 91, 155, 230, 151, 84, 89, 61, 44, 129, 54, 172, 168, 182, 164, 143, 168, 11, 115, 201, 36, 121, 0, 2, 17, 0, 0, 0, 1, 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