Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5aa4a7bf537314bb81ce69339db838792274c3161a3851903f85cf9160c8f4b

Tx prefix hash: 7273ee588bd4279a18c6ee3e4a1b82b137fdddfbbfa20b597d56d0e139a3276e
Tx public key: 345dbd2b4e25bb42a824c73372d97cb08d06c04d49c1e472d1442f1bcabf9e9c
Timestamp: 1576446514 Timestamp [UCT]: 2019-12-15 21:48:34 Age [y:d:h:m:s]: 05:080:16:07:32
Block: 27869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1204131 RingCT/type: yes/0
Extra: 01345dbd2b4e25bb42a824c73372d97cb08d06c04d49c1e472d1442f1bcabf9e9c021100000011d81c26c0000000000000000000

1 output(s) for total of 496.202901494000 dcy

stealth address amount amount idx
00: c732013ad64b9576f99434d5c0da5b879a46ed4717113412a29b93dd858fc3db 496.202901494000 46025 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": 27879, "vin": [ { "gen": { "height": 27869 } } ], "vout": [ { "amount": 496202901494, "target": { "key": "c732013ad64b9576f99434d5c0da5b879a46ed4717113412a29b93dd858fc3db" } } ], "extra": [ 1, 52, 93, 189, 43, 78, 37, 187, 66, 168, 36, 199, 51, 114, 217, 124, 176, 141, 6, 192, 77, 73, 193, 228, 114, 209, 68, 47, 27, 202, 191, 158, 156, 2, 17, 0, 0, 0, 17, 216, 28, 38, 192, 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