Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d454e8fa9c42c848ff959acdf3ab045ee5cfd861c9e398566b100e1e81546cb1

Tx prefix hash: 1d9aa96d6b4acab6585e73e6bf939ee10225b356701e031af7a87ead3a10a8e4
Tx public key: 8bad09fab500bdbe332c1c6b9290541e7de232c0ae32e81e2cf5ad1f2d38b236
Timestamp: 1587534359 Timestamp [UCT]: 2020-04-22 05:45:59 Age [y:d:h:m:s]: 04:219:08:42:00
Block: 94741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1067436 RingCT/type: yes/0
Extra: 018bad09fab500bdbe332c1c6b9290541e7de232c0ae32e81e2cf5ad1f2d38b2360211000003846fa03929000000000000000000

1 output(s) for total of 297.909605728000 dcy

stealth address amount amount idx
00: 58424e0ff8af6557ee25b84fea0feaae482212014dc8a4c2dca6dde8f196770d 297.909605728000 168583 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": 94751, "vin": [ { "gen": { "height": 94741 } } ], "vout": [ { "amount": 297909605728, "target": { "key": "58424e0ff8af6557ee25b84fea0feaae482212014dc8a4c2dca6dde8f196770d" } } ], "extra": [ 1, 139, 173, 9, 250, 181, 0, 189, 190, 51, 44, 28, 107, 146, 144, 84, 30, 125, 226, 50, 192, 174, 50, 232, 30, 44, 245, 173, 31, 45, 56, 178, 54, 2, 17, 0, 0, 3, 132, 111, 160, 57, 41, 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