Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ff0623a432bd0b1009651c24150be9011682db1c45908afd94b1442e7b027b2

Tx prefix hash: 6684d7d50778e47e592ec90a3a2ca854244db3f62a888d105eb21b15a15673f4
Tx public key: e9d51dfc5f5638c2cc4eb2f18acd5d4b690c4104c2005911d24a11e25de933c3
Timestamp: 1736982762 Timestamp [UCT]: 2025-01-15 23:12:42 Age [y:d:h:m:s]: 00:058:00:16:05
Block: 1198199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41248 RingCT/type: yes/0
Extra: 01e9d51dfc5f5638c2cc4eb2f18acd5d4b690c4104c2005911d24a11e25de933c30211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dbfec9e3ea7574a5f0a21e7b6f1808d39a4492dae1951df972bb939371ae015 0.600000000000 1684818 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": 1198209, "vin": [ { "gen": { "height": 1198199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dbfec9e3ea7574a5f0a21e7b6f1808d39a4492dae1951df972bb939371ae015" } } ], "extra": [ 1, 233, 213, 29, 252, 95, 86, 56, 194, 204, 78, 178, 241, 138, 205, 93, 75, 105, 12, 65, 4, 194, 0, 89, 17, 210, 74, 17, 226, 93, 233, 51, 195, 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