Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e21233c01ecd93b23c4bdebbedb01f25205dbca97d511a42eee49f851780b59

Tx prefix hash: d8d3083aafb0d74e980a9109a4f2d8b4bf045c18049c8dca19ee09d0850121a3
Tx public key: 4bd1192f30b2d3286e4caa9bfb435903fabcc8b8117da13c9004cebbb02d5f6d
Timestamp: 1733022874 Timestamp [UCT]: 2024-12-01 03:14:34 Age [y:d:h:m:s]: 00:343:13:05:03
Block: 1165427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243056 RingCT/type: yes/0
Extra: 014bd1192f30b2d3286e4caa9bfb435903fabcc8b8117da13c9004cebbb02d5f6d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65030878fae5012d3c8b0e69ff970a5db2f689444b2326de2eeb8140817d90a0 0.600000000000 1651102 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": 1165437, "vin": [ { "gen": { "height": 1165427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65030878fae5012d3c8b0e69ff970a5db2f689444b2326de2eeb8140817d90a0" } } ], "extra": [ 1, 75, 209, 25, 47, 48, 178, 211, 40, 110, 76, 170, 155, 251, 67, 89, 3, 250, 188, 200, 184, 17, 125, 161, 60, 144, 4, 206, 187, 176, 45, 95, 109, 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