Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef741d07ab6eee96fa5c9aa5f6c7512f75e2ee43e72e13d879e866b754653399

Tx prefix hash: 0b6fca8c406df2dc12d5852fb3147da81bc389a62f8fe1da5f156f86a21004c0
Tx public key: 5077f4bcaaa8198c04406539ac7659efc02d8bf8ccdc1bae31b14f7026fa3103
Timestamp: 1700492623 Timestamp [UCT]: 2023-11-20 15:03:43 Age [y:d:h:m:s]: 01:143:19:24:16
Block: 895827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363957 RingCT/type: yes/0
Extra: 015077f4bcaaa8198c04406539ac7659efc02d8bf8ccdc1bae31b14f7026fa310302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.660318193000 dcy

stealth address amount amount idx
00: e5cf85f398c7238fbdb25aed6efcf633a8f069ced89d297169cb5b63aa40b9a4 0.660318193000 1352074 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": 895837, "vin": [ { "gen": { "height": 895827 } } ], "vout": [ { "amount": 660318193, "target": { "key": "e5cf85f398c7238fbdb25aed6efcf633a8f069ced89d297169cb5b63aa40b9a4" } } ], "extra": [ 1, 80, 119, 244, 188, 170, 168, 25, 140, 4, 64, 101, 57, 172, 118, 89, 239, 192, 45, 139, 248, 204, 220, 27, 174, 49, 177, 79, 112, 38, 250, 49, 3, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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