Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4c30fc029aab7558a65e5c7f99b9a80f125d424b8ca3a297851d9beb6653a6e

Tx prefix hash: 81e04f57221f789fd6a59849f94276215786e8aeb32705d56f1ce3176f79f79b
Tx public key: 59e3d8115650a5e1127726a128e29b7a4f64470d0eb654f3e906ee0511fd3d17
Timestamp: 1714881811 Timestamp [UCT]: 2024-05-05 04:03:31 Age [y:d:h:m:s]: 00:334:11:35:33
Block: 1015137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239084 RingCT/type: yes/0
Extra: 0159e3d8115650a5e1127726a128e29b7a4f64470d0eb654f3e906ee0511fd3d1702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58509dc73f142e0eba41761aee41bcae903dba49b85ca234bc3bb09933291533 0.600000000000 1478416 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": 1015147, "vin": [ { "gen": { "height": 1015137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58509dc73f142e0eba41761aee41bcae903dba49b85ca234bc3bb09933291533" } } ], "extra": [ 1, 89, 227, 216, 17, 86, 80, 165, 225, 18, 119, 38, 161, 40, 226, 155, 122, 79, 100, 71, 13, 14, 182, 84, 243, 233, 6, 238, 5, 17, 253, 61, 23, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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