Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 359cadf69d884348decb40243db68efcbd43ac785246ad1cb15f05aac1dee09f

Tx prefix hash: 5dabbd09a17e50cb4335ae3d0da5a4f50d8a9171f328bebb73bc72fd6bec3326
Tx public key: 44b8317f29d73c9ec925699203c33d93c1bc8b9a562c09dd6e9e7a1d21809de6
Timestamp: 1703210314 Timestamp [UCT]: 2023-12-22 01:58:34 Age [y:d:h:m:s]: 02:017:10:02:08
Block: 918356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 532244 RingCT/type: yes/0
Extra: 0144b8317f29d73c9ec925699203c33d93c1bc8b9a562c09dd6e9e7a1d21809de60211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e26e26f2b0569fe9367f05d2042676d01f3511d7db1b02492a34b80cd02c9321 0.600000000000 1375998 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": 918366, "vin": [ { "gen": { "height": 918356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e26e26f2b0569fe9367f05d2042676d01f3511d7db1b02492a34b80cd02c9321" } } ], "extra": [ 1, 68, 184, 49, 127, 41, 215, 60, 158, 201, 37, 105, 146, 3, 195, 61, 147, 193, 188, 139, 154, 86, 44, 9, 221, 110, 158, 122, 29, 33, 128, 157, 230, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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