Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc32689df7b86dc7920d154cca99dc4ea56aab1508f4c7cf67593ff2fb64dfe5

Tx prefix hash: 54839828702dc880253bcbf7a94a072f3ff2c9841dd534de8db99f07f3a7ef93
Tx public key: c0b8cd9e0e64f382fa3dc862d9bce645d9d8e8e8227e12ba2d32c4fb32b69783
Timestamp: 1713428843 Timestamp [UCT]: 2024-04-18 08:27:23 Age [y:d:h:m:s]: 00:156:14:08:09
Block: 1003061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112184 RingCT/type: yes/0
Extra: 01c0b8cd9e0e64f382fa3dc862d9bce645d9d8e8e8227e12ba2d32c4fb32b6978302110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fb9b5b22102604a2d080dac1ed414fe5f4d1d6482db57be1b688b15a57a2d92 0.600000000000 1463591 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": 1003071, "vin": [ { "gen": { "height": 1003061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fb9b5b22102604a2d080dac1ed414fe5f4d1d6482db57be1b688b15a57a2d92" } } ], "extra": [ 1, 192, 184, 205, 158, 14, 100, 243, 130, 250, 61, 200, 98, 217, 188, 230, 69, 217, 216, 232, 232, 34, 126, 18, 186, 45, 50, 196, 251, 50, 182, 151, 131, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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