Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84a877980a89ce13772106e5b5e63c59b8398e461cf6bc50b2fb15903086a9ae

Tx prefix hash: 31b73816ca5e58c9a4644faf40af006ee0b610c11c66bc0cdfe0dd0ba990116d
Tx public key: bc22a8fba3d7a46dcb9044764ab37a04b7494c1f281e5c92702cbc3a8bccb05f
Timestamp: 1636999264 Timestamp [UCT]: 2021-11-15 18:01:04 Age [y:d:h:m:s]: 03:043:20:35:40
Block: 374967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 810096 RingCT/type: yes/0
Extra: 01bc22a8fba3d7a46dcb9044764ab37a04b7494c1f281e5c92702cbc3a8bccb05f021100000001379224c2000000000000000000

1 output(s) for total of 35.121985544000 dcy

stealth address amount amount idx
00: 951ab981910ce60ad624247a0bd097505aa193f59f77daac35c9839bbe708462 35.121985544000 758829 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": 374977, "vin": [ { "gen": { "height": 374967 } } ], "vout": [ { "amount": 35121985544, "target": { "key": "951ab981910ce60ad624247a0bd097505aa193f59f77daac35c9839bbe708462" } } ], "extra": [ 1, 188, 34, 168, 251, 163, 215, 164, 109, 203, 144, 68, 118, 74, 179, 122, 4, 183, 73, 76, 31, 40, 30, 92, 146, 112, 44, 188, 58, 139, 204, 176, 95, 2, 17, 0, 0, 0, 1, 55, 146, 36, 194, 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