Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5e0a5dc8162075fe370c22aafd18a5cb43cf540804644a2793bc17a146fd570

Tx prefix hash: f12ede6d5bdf7a2905cda4b715fba928bb2766c806b85afdb519ce8bb4ede228
Tx public key: 3b39f6c176551e919cdc86e6347f720762720ed4f03a54630b6f6dc80046c506
Timestamp: 1697209987 Timestamp [UCT]: 2023-10-13 15:13:07 Age [y:d:h:m:s]: 01:110:21:46:58
Block: 868818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340266 RingCT/type: yes/0
Extra: 013b39f6c176551e919cdc86e6347f720762720ed4f03a54630b6f6dc80046c50602110000000133af99f4000000000000000000

1 output(s) for total of 0.811419297000 dcy

stealth address amount amount idx
00: 22affbaa0056b0f6d27adeca2f237181a94d0478ae3f4a83929f0e2298abfbd4 0.811419297000 1323637 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": 868828, "vin": [ { "gen": { "height": 868818 } } ], "vout": [ { "amount": 811419297, "target": { "key": "22affbaa0056b0f6d27adeca2f237181a94d0478ae3f4a83929f0e2298abfbd4" } } ], "extra": [ 1, 59, 57, 246, 193, 118, 85, 30, 145, 156, 220, 134, 230, 52, 127, 114, 7, 98, 114, 14, 212, 240, 58, 84, 99, 11, 111, 109, 200, 0, 70, 197, 6, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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