Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7b65b6427a2ac57b911f6f105e274becb248a5602648e715d3c3d85cb507192

Tx prefix hash: 452fee7b2ba53fff2305137545e2585a30374f9946995e87cb0039cc5dc2ef9e
Tx public key: 80ebd47736264c81e9315026ea488abda1295c2f3a5683c5ea1125d917f8f105
Timestamp: 1731838717 Timestamp [UCT]: 2024-11-17 10:18:37 Age [y:d:h:m:s]: 00:143:13:07:12
Block: 1155607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102415 RingCT/type: yes/0
Extra: 0180ebd47736264c81e9315026ea488abda1295c2f3a5683c5ea1125d917f8f105021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3cdf65ec26bf1e2099e7fb735f8d9bc82b4dc1af534cc6a67b9d3e250b57ede 0.600000000000 1641224 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": 1155617, "vin": [ { "gen": { "height": 1155607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3cdf65ec26bf1e2099e7fb735f8d9bc82b4dc1af534cc6a67b9d3e250b57ede" } } ], "extra": [ 1, 128, 235, 212, 119, 54, 38, 76, 129, 233, 49, 80, 38, 234, 72, 138, 189, 161, 41, 92, 47, 58, 86, 131, 197, 234, 17, 37, 217, 23, 248, 241, 5, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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