Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69d814672cc1dfd1c81942a537e5dbdf183ddd90e41f97b9af52fe5fc8fff30e

Tx prefix hash: 0ffff6b52eee57fcbb4f229aaff5bf120ae4511f4932aacdf7200886d4464306
Tx public key: 0f68832348fcea0e7d2ced67703c1db12de41a7e4ca5b0b8959606d5a7c04878
Timestamp: 1731456456 Timestamp [UCT]: 2024-11-13 00:07:36 Age [y:d:h:m:s]: 00:192:03:35:52
Block: 1152431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137215 RingCT/type: yes/0
Extra: 010f68832348fcea0e7d2ced67703c1db12de41a7e4ca5b0b8959606d5a7c048780211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e92303a80c51858d00b096e9509d1fb84db3a1ceb902c8f223bc2f9799ad6bfb 0.600000000000 1638028 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": 1152441, "vin": [ { "gen": { "height": 1152431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e92303a80c51858d00b096e9509d1fb84db3a1ceb902c8f223bc2f9799ad6bfb" } } ], "extra": [ 1, 15, 104, 131, 35, 72, 252, 234, 14, 125, 44, 237, 103, 112, 60, 29, 177, 45, 228, 26, 126, 76, 165, 176, 184, 149, 150, 6, 213, 167, 192, 72, 120, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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