Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35443e7eac4ee15897001ed931f16fa05fbf6e3b3cd7d4ad761b231cf0bf9cda

Tx prefix hash: 6951656c6ffc169e251cd91fd61b677177984d9bd4d2a93926409fcc2d0f6ed6
Tx public key: 644b929f73dab0cb196f641faa2387dc3a8db1f17a003379d0b2bef6b97e79e8
Timestamp: 1732286678 Timestamp [UCT]: 2024-11-22 14:44:38 Age [y:d:h:m:s]: 00:346:18:09:05
Block: 1159320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245359 RingCT/type: yes/0
Extra: 01644b929f73dab0cb196f641faa2387dc3a8db1f17a003379d0b2bef6b97e79e80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6cdafb6f459442bf14623fbfa2fbc80724258bffa6cd714da4879b721d22007 0.600000000000 1644953 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": 1159330, "vin": [ { "gen": { "height": 1159320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6cdafb6f459442bf14623fbfa2fbc80724258bffa6cd714da4879b721d22007" } } ], "extra": [ 1, 100, 75, 146, 159, 115, 218, 176, 203, 25, 111, 100, 31, 170, 35, 135, 220, 58, 141, 177, 241, 122, 0, 51, 121, 208, 178, 190, 246, 185, 126, 121, 232, 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