Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f11991df267933de4b2f2f7ccbdd4686354ef79010bb939f469ea0dcbe1472

Tx prefix hash: eea2e1742ea498fc9e6e6c99f261199b03de39a01db2d447e73de00fe90aeb47
Tx public key: b45277b81b1b6774b0d24b27e7ca9c512256c21972e1e51eaad4c4fd910988c7
Timestamp: 1734968112 Timestamp [UCT]: 2024-12-23 15:35:12 Age [y:d:h:m:s]: 00:095:14:43:20
Block: 1181559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68085 RingCT/type: yes/0
Extra: 01b45277b81b1b6774b0d24b27e7ca9c512256c21972e1e51eaad4c4fd910988c70211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7faa58c1fac272eebbedfbe7febb6f8a387caa9d7adbc89d2f01164da74b9144 0.600000000000 1667984 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": 1181569, "vin": [ { "gen": { "height": 1181559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7faa58c1fac272eebbedfbe7febb6f8a387caa9d7adbc89d2f01164da74b9144" } } ], "extra": [ 1, 180, 82, 119, 184, 27, 27, 103, 116, 176, 210, 75, 39, 231, 202, 156, 81, 34, 86, 194, 25, 114, 225, 229, 30, 170, 212, 196, 253, 145, 9, 136, 199, 2, 17, 0, 0, 0, 4, 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