Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 462c80ba40432f01916033ee5c629428416861edad10aa48eb0d0b746d074e72

Tx prefix hash: f794bee69de8132305ad9ab0be7082e6822d06f494c4f7be5a85861ea96c8145
Tx public key: 6fb1b3dde455859b3219d6709d0b5ad158d9e0367a24e9966260463a8cc40606
Timestamp: 1694936644 Timestamp [UCT]: 2023-09-17 07:44:04 Age [y:d:h:m:s]: 01:199:06:42:22
Block: 849955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403507 RingCT/type: yes/0
Extra: 016fb1b3dde455859b3219d6709d0b5ad158d9e0367a24e9966260463a8cc40606021100000005faf35c9c000000000000000000

1 output(s) for total of 0.937014494000 dcy

stealth address amount amount idx
00: 4c0f1352e9ffda285e0d9913823c3caef33a2d1c7a3f4f3024c3df657b898450 0.937014494000 1303645 of 0

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": 849965, "vin": [ { "gen": { "height": 849955 } } ], "vout": [ { "amount": 937014494, "target": { "key": "4c0f1352e9ffda285e0d9913823c3caef33a2d1c7a3f4f3024c3df657b898450" } } ], "extra": [ 1, 111, 177, 179, 221, 228, 85, 133, 155, 50, 25, 214, 112, 157, 11, 90, 209, 88, 217, 224, 54, 122, 36, 233, 150, 98, 96, 70, 58, 140, 196, 6, 6, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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