Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fe4a5958d12a0a8a484761988021bbfc799bbe0a1336d092671eea0288c04a2

Tx prefix hash: 40715a764953d4acc2d58de674a7b390e5d5d7159eca0abf4856bd856d86e69d
Tx public key: 8dc45a82a5c9d77eeb05f3d230773baf3dbc528490c6c4c9bfa11e4a1616536a
Timestamp: 1648284706 Timestamp [UCT]: 2022-03-26 08:51:46 Age [y:d:h:m:s]: 02:354:07:01:46
Block: 466684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 772546 RingCT/type: yes/0
Extra: 018dc45a82a5c9d77eeb05f3d230773baf3dbc528490c6c4c9bfa11e4a1616536a021100000004a272b9cb000000000000000000

1 output(s) for total of 17.445460290000 dcy

stealth address amount amount idx
00: bccf972252ecebb5a01a2d6ec468f1e450dced6f9170d00481f36c019f62c52f 17.445460290000 885047 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": 466694, "vin": [ { "gen": { "height": 466684 } } ], "vout": [ { "amount": 17445460290, "target": { "key": "bccf972252ecebb5a01a2d6ec468f1e450dced6f9170d00481f36c019f62c52f" } } ], "extra": [ 1, 141, 196, 90, 130, 165, 201, 215, 126, 235, 5, 243, 210, 48, 119, 59, 175, 61, 188, 82, 132, 144, 198, 196, 201, 191, 161, 30, 74, 22, 22, 83, 106, 2, 17, 0, 0, 0, 4, 162, 114, 185, 203, 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