Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18653b8d2ad93f174cf01426af352ae69f5d017367901cd32807bc37b403d291

Tx prefix hash: 937c9bde4c21c958be8dd778837bb8e9b312f81e9ceac9c5d7f4b37f79b5be60
Tx public key: 8b4e34dc9cbf3c58f288d9a0f91bd213e1bc2d0c3ffc93add548e0557b85aeda
Timestamp: 1732542208 Timestamp [UCT]: 2024-11-25 13:43:28 Age [y:d:h:m:s]: 00:124:03:42:50
Block: 1161440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88540 RingCT/type: yes/0
Extra: 018b4e34dc9cbf3c58f288d9a0f91bd213e1bc2d0c3ffc93add548e0557b85aeda0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76a9e8b8b0e4b000002441ac13feaa60d6e6c218e87f44d63f7264687aab9ca1 0.600000000000 1647095 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": 1161450, "vin": [ { "gen": { "height": 1161440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76a9e8b8b0e4b000002441ac13feaa60d6e6c218e87f44d63f7264687aab9ca1" } } ], "extra": [ 1, 139, 78, 52, 220, 156, 191, 60, 88, 242, 136, 217, 160, 249, 27, 210, 19, 225, 188, 45, 12, 63, 252, 147, 173, 213, 72, 224, 85, 123, 133, 174, 218, 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