Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379e976319493ae41ebb5efb884ff7e9502514c0ea799d5c673b4ee7c84edda4

Tx prefix hash: 6d67160efb5a7e91671ea35db6dd0d64fdd9907c4c1d708b687ac53683c5fd68
Tx public key: 15f78b4a0631f469bdf8a066284e7dbbf43d6ccc7d397cb4f11de595ef6068cf
Timestamp: 1584527813 Timestamp [UCT]: 2020-03-18 10:36:53 Age [y:d:h:m:s]: 04:296:17:15:16
Block: 84929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107695 RingCT/type: yes/0
Extra: 0115f78b4a0631f469bdf8a066284e7dbbf43d6ccc7d397cb4f11de595ef6068cf02110000000369b04ac4000000000000000000

1 output(s) for total of 321.067059098000 dcy

stealth address amount amount idx
00: 9f67863357789b440c1ea512a19be4e8a86b2a0eb43bf95105d74bc32445cd87 321.067059098000 153721 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": 84939, "vin": [ { "gen": { "height": 84929 } } ], "vout": [ { "amount": 321067059098, "target": { "key": "9f67863357789b440c1ea512a19be4e8a86b2a0eb43bf95105d74bc32445cd87" } } ], "extra": [ 1, 21, 247, 139, 74, 6, 49, 244, 105, 189, 248, 160, 102, 40, 78, 125, 187, 244, 61, 108, 204, 125, 57, 124, 180, 241, 29, 229, 149, 239, 96, 104, 207, 2, 17, 0, 0, 0, 3, 105, 176, 74, 196, 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