Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11f9c08dcd67b20cb91ab398d71f84aa436c37a0f088ca37d165ab26dee4dbc9

Tx prefix hash: d290fdfb3da1f30eb4e01805f7ae60a6686bdcb746422461d275e9c7fac8b289
Tx public key: 1afecc56930dd9958b7a50a9e431778d92e70707b7f5f9c5963dffc33028d270
Timestamp: 1738475915 Timestamp [UCT]: 2025-02-02 05:58:35 Age [y:d:h:m:s]: 00:289:08:41:10
Block: 1210294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204577 RingCT/type: yes/0
Extra: 011afecc56930dd9958b7a50a9e431778d92e70707b7f5f9c5963dffc33028d270021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5692b7aacbb0961526958a2c3aa56028584ca6d210ae004a6e34d2174a1a0a7c 0.600000000000 1697045 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": 1210304, "vin": [ { "gen": { "height": 1210294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5692b7aacbb0961526958a2c3aa56028584ca6d210ae004a6e34d2174a1a0a7c" } } ], "extra": [ 1, 26, 254, 204, 86, 147, 13, 217, 149, 139, 122, 80, 169, 228, 49, 119, 141, 146, 231, 7, 7, 183, 245, 249, 197, 150, 61, 255, 195, 48, 40, 210, 112, 2, 17, 0, 0, 0, 4, 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