Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7eb1713a12ac05b9f0da4dd5158b92d557704ea792ecef94dee67678385a5c34

Tx prefix hash: e204da82da7da14b0dd0809dd5833a13ebfbedf0bfb0f89da64bfbb0a301a326
Tx public key: bf6e4987e4b299afcd3b336e90a66da259d99e7455f5a432fcdcc631e481a6be
Timestamp: 1703324064 Timestamp [UCT]: 2023-12-23 09:34:24 Age [y:d:h:m:s]: 01:105:16:07:04
Block: 919298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336637 RingCT/type: yes/0
Extra: 01bf6e4987e4b299afcd3b336e90a66da259d99e7455f5a432fcdcc631e481a6be0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ec5846716235413cacd9a20e95aea5f19b16e435098e3d8c22b55a25bffa8ce 0.600000000000 1376966 of 15

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": 919308, "vin": [ { "gen": { "height": 919298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ec5846716235413cacd9a20e95aea5f19b16e435098e3d8c22b55a25bffa8ce" } } ], "extra": [ 1, 191, 110, 73, 135, 228, 178, 153, 175, 205, 59, 51, 110, 144, 166, 109, 162, 89, 217, 158, 116, 85, 245, 164, 50, 252, 220, 198, 49, 228, 129, 166, 190, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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