Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a31f19747c54ea024ec06c9351379265bf1ec37a6acc0c7a51c4ca9a9715711a

Tx prefix hash: 0f116697cf2bcdaae17f0d6aed12cc97687c1b9106a35299809cbb10fa094442
Tx public key: cfafe5acc3cbaff555128dee97a2fdabf607f35bdbd4958cb6fce3d34e8e6e1a
Timestamp: 1715454832 Timestamp [UCT]: 2024-05-11 19:13:52 Age [y:d:h:m:s]: 00:333:13:20:24
Block: 1019903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238396 RingCT/type: yes/0
Extra: 01cfafe5acc3cbaff555128dee97a2fdabf607f35bdbd4958cb6fce3d34e8e6e1a02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6eedfa5bc4098d421ada6611c8baff7ae1d953ab760a10d846ea01cfa46069e 0.600000000000 1483956 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": 1019913, "vin": [ { "gen": { "height": 1019903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6eedfa5bc4098d421ada6611c8baff7ae1d953ab760a10d846ea01cfa46069e" } } ], "extra": [ 1, 207, 175, 229, 172, 195, 203, 175, 245, 85, 18, 141, 238, 151, 162, 253, 171, 246, 7, 243, 91, 219, 212, 149, 140, 182, 252, 227, 211, 78, 142, 110, 26, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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