Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 129f7f147911834881caec5638bda8fdcef67570def505a5b7297ece04264aed

Tx prefix hash: 286406a95fbb029873f5c2582c62aa18892cd0948c28f0828589530b26a064ee
Tx public key: f8fe95b59d6e6729a5d56f1a841328c2ff940f4474c17ae3db57be56580557fd
Timestamp: 1696955669 Timestamp [UCT]: 2023-10-10 16:34:29 Age [y:d:h:m:s]: 01:105:11:19:02
Block: 866722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336592 RingCT/type: yes/0
Extra: 01f8fe95b59d6e6729a5d56f1a841328c2ff940f4474c17ae3db57be56580557fd02110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.824499227000 dcy

stealth address amount amount idx
00: dfc7b415dbf6770be512badc039f3dc511dd1fb15917d707bcea53a27712f21d 0.824499227000 1321350 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": 866732, "vin": [ { "gen": { "height": 866722 } } ], "vout": [ { "amount": 824499227, "target": { "key": "dfc7b415dbf6770be512badc039f3dc511dd1fb15917d707bcea53a27712f21d" } } ], "extra": [ 1, 248, 254, 149, 181, 157, 110, 103, 41, 165, 213, 111, 26, 132, 19, 40, 194, 255, 148, 15, 68, 116, 193, 122, 227, 219, 87, 190, 86, 88, 5, 87, 253, 2, 17, 0, 0, 0, 12, 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