Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad7c2af474ba35f8f485340d593c53a87381f12d7567cd5fc191f5ccff747800

Tx prefix hash: 46fbb081ebdb0e89d5d8c050e805232829e73ea39cc3ac38275ffe8e027ea39c
Tx public key: 8e4b2bd9b389de6ae650d7ab04e0bf23c03b7c9cb40cec6aa19bfabadaf064ee
Timestamp: 1721347210 Timestamp [UCT]: 2024-07-19 00:00:10 Age [y:d:h:m:s]: 00:259:01:53:56
Block: 1068737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185060 RingCT/type: yes/0
Extra: 018e4b2bd9b389de6ae650d7ab04e0bf23c03b7c9cb40cec6aa19bfabadaf064ee02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: daea4f5024e647036c2c5658a4f186fae1a362da5dbf7804002e70f779d400db 0.600000000000 1539886 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": 1068747, "vin": [ { "gen": { "height": 1068737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "daea4f5024e647036c2c5658a4f186fae1a362da5dbf7804002e70f779d400db" } } ], "extra": [ 1, 142, 75, 43, 217, 179, 137, 222, 106, 230, 80, 215, 171, 4, 224, 191, 35, 192, 59, 124, 156, 180, 12, 236, 106, 161, 155, 250, 186, 218, 240, 100, 238, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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