Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a8d895d3671fe50fc2454063033f1056160e0303a5d4414350a6de308c851de

Tx prefix hash: 2982803a1482acc69c8f2772441f0be8fcafb2c30a9c8f4bb5abf5d529bdd2aa
Tx public key: 46aac51e32feda2f583515d2ee57d61dad2d7f659c6e9b81373bfdc250485e9e
Timestamp: 1728344636 Timestamp [UCT]: 2024-10-07 23:43:56 Age [y:d:h:m:s]: 01:033:18:48:29
Block: 1126743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282516 RingCT/type: yes/0
Extra: 0146aac51e32feda2f583515d2ee57d61dad2d7f659c6e9b81373bfdc250485e9e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33fb3724130c7606066216883b3bafd8d44b6fb4010e7c73705bb4df89764b60 0.600000000000 1609538 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": 1126753, "vin": [ { "gen": { "height": 1126743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33fb3724130c7606066216883b3bafd8d44b6fb4010e7c73705bb4df89764b60" } } ], "extra": [ 1, 70, 170, 197, 30, 50, 254, 218, 47, 88, 53, 21, 210, 238, 87, 214, 29, 173, 45, 127, 101, 156, 110, 155, 129, 55, 59, 253, 194, 80, 72, 94, 158, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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