Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f1c8a7879a8abf6651f90470bc68b2c0d4b155d5440d25b0b5d93bc4498b72f

Tx prefix hash: 00586f03b7a9800837d08fe7ddbbd5cdfc139b833b4279b93e5f9ad93838d182
Tx public key: 517167d790bfdb87a2ffaeae3da4fbfd9523016d62cb93036c3bf8c64f70c752
Timestamp: 1734834674 Timestamp [UCT]: 2024-12-22 02:31:14 Age [y:d:h:m:s]: 00:108:02:37:00
Block: 1180456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77020 RingCT/type: yes/0
Extra: 01517167d790bfdb87a2ffaeae3da4fbfd9523016d62cb93036c3bf8c64f70c752021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d10c11486e8a7641b0e369b52b552914d394cc4e5e0d6847f191838f2ab5adc8 0.600000000000 1666867 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": 1180466, "vin": [ { "gen": { "height": 1180456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d10c11486e8a7641b0e369b52b552914d394cc4e5e0d6847f191838f2ab5adc8" } } ], "extra": [ 1, 81, 113, 103, 215, 144, 191, 219, 135, 162, 255, 174, 174, 61, 164, 251, 253, 149, 35, 1, 109, 98, 203, 147, 3, 108, 59, 248, 198, 79, 112, 199, 82, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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