Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19de309fe5f4fe7a07a2d506b80b322102cb66062e5bfcbba1a505256c12b69d

Tx prefix hash: 0198640d56e53903fff5b8987c0bcb1b4b0184e8401b1a3b1adfe8d63f1ceb80
Tx public key: 684f87a7eb6a50112b89de2c1c04006ebadbed2c20ccd215feefecba62e74e1f
Timestamp: 1714039609 Timestamp [UCT]: 2024-04-25 10:06:49 Age [y:d:h:m:s]: 00:204:00:25:05
Block: 1008140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146046 RingCT/type: yes/0
Extra: 01684f87a7eb6a50112b89de2c1c04006ebadbed2c20ccd215feefecba62e74e1f0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf153b7c0be513ab748d9c3d92f00298e3418733a31a6d89d0976bb45df9426e 0.600000000000 1469606 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": 1008150, "vin": [ { "gen": { "height": 1008140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf153b7c0be513ab748d9c3d92f00298e3418733a31a6d89d0976bb45df9426e" } } ], "extra": [ 1, 104, 79, 135, 167, 235, 106, 80, 17, 43, 137, 222, 44, 28, 4, 0, 110, 186, 219, 237, 44, 32, 204, 210, 21, 254, 239, 236, 186, 98, 231, 78, 31, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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