Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6ead5915d8b5f54a753da6d5cb7b556e374bded55309d214ef3a58a5cdc3cd9

Tx prefix hash: 29ca0735c6aab309865d22fa611fa322c2a68c7559369b08f26abbc0b5579e32
Tx public key: c39a0b6d9a221f9fd0dd49defae5345734a0023a9ee54e055dd3448598af7887
Timestamp: 1673467046 Timestamp [UCT]: 2023-01-11 19:57:26 Age [y:d:h:m:s]: 02:122:11:07:04
Block: 672638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 609217 RingCT/type: yes/0
Extra: 01c39a0b6d9a221f9fd0dd49defae5345734a0023a9ee54e055dd3448598af788702110000000652542ceb000000000000000000

1 output(s) for total of 3.624691372000 dcy

stealth address amount amount idx
00: 1f0f0b5b71a57031a366c05714737e5e6fac55f0daf784652f7d95346709a86c 3.624691372000 1114199 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": 672648, "vin": [ { "gen": { "height": 672638 } } ], "vout": [ { "amount": 3624691372, "target": { "key": "1f0f0b5b71a57031a366c05714737e5e6fac55f0daf784652f7d95346709a86c" } } ], "extra": [ 1, 195, 154, 11, 109, 154, 34, 31, 159, 208, 221, 73, 222, 250, 229, 52, 87, 52, 160, 2, 58, 158, 229, 78, 5, 93, 211, 68, 133, 152, 175, 120, 135, 2, 17, 0, 0, 0, 6, 82, 84, 44, 235, 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