Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e4f32ee5be589bf1e59d65cb331afeca226723ebb4a1ef74c290c1b280caced

Tx prefix hash: 68b9dda6d5757954eb3cc9e2eb16f0e6e239e1cce62d26bdd6b452057c969c3b
Tx public key: 9a68a4a98dd585d2bbc58adc713a8972b982352af39f557af9d5d6b6a47ed1d7
Timestamp: 1703354299 Timestamp [UCT]: 2023-12-23 17:58:19 Age [y:d:h:m:s]: 01:138:03:20:27
Block: 919551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359872 RingCT/type: yes/0
Extra: 019a68a4a98dd585d2bbc58adc713a8972b982352af39f557af9d5d6b6a47ed1d70211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df68bb2ceee14042d72ac142ef592575e7323b4d4fb62bdcf51d8a75d88ab2dd 0.600000000000 1377225 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": 919561, "vin": [ { "gen": { "height": 919551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df68bb2ceee14042d72ac142ef592575e7323b4d4fb62bdcf51d8a75d88ab2dd" } } ], "extra": [ 1, 154, 104, 164, 169, 141, 213, 133, 210, 187, 197, 138, 220, 113, 58, 137, 114, 185, 130, 53, 42, 243, 159, 85, 122, 249, 213, 214, 182, 164, 126, 209, 215, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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