Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0595f1a5ca6eee1ed6beea3bd7ffbdae904695a589cd455b23cda8c36c0eaaae

Tx prefix hash: 49083bce31df3d98ead7ceddc479364c9b5deb8c79e71308c5f0768e276cb63e
Tx public key: 319c5d2862f3f65caf994114dacede5a6636a6a312cf40cabe515207b98c2a9e
Timestamp: 1581251349 Timestamp [UCT]: 2020-02-09 12:29:09 Age [y:d:h:m:s]: 05:269:11:27:56
Block: 61380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1343023 RingCT/type: yes/0
Extra: 01319c5d2862f3f65caf994114dacede5a6636a6a312cf40cabe515207b98c2a9e02110000008212c4732d000000000000000000

1 output(s) for total of 384.258423164000 dcy

stealth address amount amount idx
00: d1f4e6c159255d94a0bbbb077cd525aecc881f455f4202d436a272d572c1ec22 384.258423164000 113107 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": 61390, "vin": [ { "gen": { "height": 61380 } } ], "vout": [ { "amount": 384258423164, "target": { "key": "d1f4e6c159255d94a0bbbb077cd525aecc881f455f4202d436a272d572c1ec22" } } ], "extra": [ 1, 49, 156, 93, 40, 98, 243, 246, 92, 175, 153, 65, 20, 218, 206, 222, 90, 102, 54, 166, 163, 18, 207, 64, 202, 190, 81, 82, 7, 185, 140, 42, 158, 2, 17, 0, 0, 0, 130, 18, 196, 115, 45, 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