Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65157759cdb78d3bdf48f577e67b494283484d25e563198e2e5f3214f3d8b322

Tx prefix hash: 308162ef98049a9348d4b503992d900915201b1b19806909c491babe6832b3dc
Tx public key: 62d290c7d673026ee418043bd297c2419122a63b1efe5e1c0ee93a79cf041f6d
Timestamp: 1700797315 Timestamp [UCT]: 2023-11-24 03:41:55 Age [y:d:h:m:s]: 00:357:00:21:54
Block: 898351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255642 RingCT/type: yes/0
Extra: 0162d290c7d673026ee418043bd297c2419122a63b1efe5e1c0ee93a79cf041f6d021100000003faf35c9c000000000000000000

1 output(s) for total of 0.647724314000 dcy

stealth address amount amount idx
00: 5079c5d99cc1fa90e8dc25b782c5799d1b674e7771aa56984e6425f557728931 0.647724314000 1354764 of 0

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": 898361, "vin": [ { "gen": { "height": 898351 } } ], "vout": [ { "amount": 647724314, "target": { "key": "5079c5d99cc1fa90e8dc25b782c5799d1b674e7771aa56984e6425f557728931" } } ], "extra": [ 1, 98, 210, 144, 199, 214, 115, 2, 110, 228, 24, 4, 59, 210, 151, 194, 65, 145, 34, 166, 59, 30, 254, 94, 28, 14, 233, 58, 121, 207, 4, 31, 109, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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