Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a47e7a1d88c5743fae8e2715b1b3def29bd3782bf69a94c0984bd99ed5ebe3a1

Tx prefix hash: d2aeea77f92fee75a936f4bc571eacd52af68fbc062f0878b4bcb1be7079188e
Tx public key: 08616e943cc4ef212075fd293f98e861946fddcace449e27a37ddf5a916feb65
Timestamp: 1704332151 Timestamp [UCT]: 2024-01-04 01:35:51 Age [y:d:h:m:s]: 01:095:13:07:37
Block: 927671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329377 RingCT/type: yes/0
Extra: 0108616e943cc4ef212075fd293f98e861946fddcace449e27a37ddf5a916feb6502110000000839e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 247394c4b6400fd9f90b71d3ed3c4740a1aa42fa3a1f8ac5537bd22b3ee30c18 0.600000000000 1385507 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": 927681, "vin": [ { "gen": { "height": 927671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "247394c4b6400fd9f90b71d3ed3c4740a1aa42fa3a1f8ac5537bd22b3ee30c18" } } ], "extra": [ 1, 8, 97, 110, 148, 60, 196, 239, 33, 32, 117, 253, 41, 63, 152, 232, 97, 148, 111, 221, 202, 206, 68, 158, 39, 163, 125, 223, 90, 145, 111, 235, 101, 2, 17, 0, 0, 0, 8, 57, 225, 213, 211, 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