Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8915544f82b5ab53929447a4d028766cf7895946e58f2334e333283b1c7f2fbd

Tx prefix hash: 0470afc9d0abd1bb52bf5fd745615a6327f07464c807c0635b0b65b03c81cc44
Tx public key: d2cd0b8c79009399158224e4895411cb0c29e3784c7bf224accfd0e20a3b9bba
Timestamp: 1730033692 Timestamp [UCT]: 2024-10-27 12:54:52 Age [y:d:h:m:s]: 00:238:15:34:02
Block: 1140694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170213 RingCT/type: yes/0
Extra: 01d2cd0b8c79009399158224e4895411cb0c29e3784c7bf224accfd0e20a3b9bba021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d40a18412fe21a7bf3f6dcdce404caa3f4d62185359cec9948131385653f04c 0.600000000000 1624497 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": 1140704, "vin": [ { "gen": { "height": 1140694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d40a18412fe21a7bf3f6dcdce404caa3f4d62185359cec9948131385653f04c" } } ], "extra": [ 1, 210, 205, 11, 140, 121, 0, 147, 153, 21, 130, 36, 228, 137, 84, 17, 203, 12, 41, 227, 120, 76, 123, 242, 36, 172, 207, 208, 226, 10, 59, 155, 186, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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