Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a6d1d27ff1cade57128395a35e9a9eaed815fc60f5bef52801d14cdb066fe9e

Tx prefix hash: 2fbd1a10813cf448fb905b0a5d4486e12772724cb4bfde9067b936b32cb6cb1a
Tx public key: 1326dd7386d0e30c99a0afaec3e267ac0496ed8495e68348eb3de91c21361e1f
Timestamp: 1711327954 Timestamp [UCT]: 2024-03-25 00:52:34 Age [y:d:h:m:s]: 01:064:19:32:02
Block: 985680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307322 RingCT/type: yes/0
Extra: 011326dd7386d0e30c99a0afaec3e267ac0496ed8495e68348eb3de91c21361e1f0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14cf44cda0d4e5eb2416b33f000a34501bc2326e0572752fbeb5bdabd6d363ec 0.600000000000 1445897 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": 985690, "vin": [ { "gen": { "height": 985680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14cf44cda0d4e5eb2416b33f000a34501bc2326e0572752fbeb5bdabd6d363ec" } } ], "extra": [ 1, 19, 38, 221, 115, 134, 208, 227, 12, 153, 160, 175, 174, 195, 226, 103, 172, 4, 150, 237, 132, 149, 230, 131, 72, 235, 61, 233, 28, 33, 54, 30, 31, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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