Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 069c8f74edf29301056caddd626510294856502d8795a2a816044ec37c8bdaca

Tx prefix hash: 5d6f572df6eeda1bb85ac6f663389c9bd28de809378a242c42626d26e73b15f4
Tx public key: 18c5e011b7ab6e5ba12d7d6ffb1aad6ae7c62cede2a00a5e076ecbd34c22b208
Timestamp: 1734504740 Timestamp [UCT]: 2024-12-18 06:52:20 Age [y:d:h:m:s]: 00:110:04:38:53
Block: 1177724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78514 RingCT/type: yes/0
Extra: 0118c5e011b7ab6e5ba12d7d6ffb1aad6ae7c62cede2a00a5e076ecbd34c22b2080211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48001fba4cd62595fffff6040dc24934321cfa6391b2e64ebae1981e1e9f3be7 0.600000000000 1664101 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": 1177734, "vin": [ { "gen": { "height": 1177724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48001fba4cd62595fffff6040dc24934321cfa6391b2e64ebae1981e1e9f3be7" } } ], "extra": [ 1, 24, 197, 224, 17, 183, 171, 110, 91, 161, 45, 125, 111, 251, 26, 173, 106, 231, 198, 44, 237, 226, 160, 10, 94, 7, 110, 203, 211, 76, 34, 178, 8, 2, 17, 0, 0, 0, 1, 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