Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8e2cb994e8ff243aa62ca5626108b2c643cfab085664eee7e55969183cd826d

Tx prefix hash: d1fb6ed261f5ea72b435c2abb11eaf1d75a104027f23e57b1f36de055e6871e1
Tx public key: 1290fd6ddb23de0df2b5bb22b681358a08b61124f6d12c6f95d5fd8c8b50fffd
Timestamp: 1717738239 Timestamp [UCT]: 2024-06-07 05:30:39 Age [y:d:h:m:s]: 00:285:18:05:21
Block: 1038812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204225 RingCT/type: yes/0
Extra: 011290fd6ddb23de0df2b5bb22b681358a08b61124f6d12c6f95d5fd8c8b50fffd021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1da34696be4ac843dbe52182d1445f8f017e1720ab48d0ef241fd168896f9e52 0.600000000000 1507373 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": 1038822, "vin": [ { "gen": { "height": 1038812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1da34696be4ac843dbe52182d1445f8f017e1720ab48d0ef241fd168896f9e52" } } ], "extra": [ 1, 18, 144, 253, 109, 219, 35, 222, 13, 242, 181, 187, 34, 182, 129, 53, 138, 8, 182, 17, 36, 246, 209, 44, 111, 149, 213, 253, 140, 139, 80, 255, 253, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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