Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d6e9ad5b8fd723cf854dd661e3af2d70925add6704c37f9775bc5a865ee8035

Tx prefix hash: a0c9fd6247a49b1430f0d9729d29fe4e548a5ac94523ec1ce4ffaa150269984b
Tx public key: 949c9705a951e86b9d8e381f3d1061adb356caf717ab4e98ebfbc53b129e43b7
Timestamp: 1722200649 Timestamp [UCT]: 2024-07-28 21:04:09 Age [y:d:h:m:s]: 00:087:19:29:12
Block: 1075793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62864 RingCT/type: yes/0
Extra: 01949c9705a951e86b9d8e381f3d1061adb356caf717ab4e98ebfbc53b129e43b702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9517dc0d0110930b62b9c24e7b67c646d92b44cfa60151c8c1e92ca0cd4227a2 0.600000000000 1548322 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": 1075803, "vin": [ { "gen": { "height": 1075793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9517dc0d0110930b62b9c24e7b67c646d92b44cfa60151c8c1e92ca0cd4227a2" } } ], "extra": [ 1, 148, 156, 151, 5, 169, 81, 232, 107, 157, 142, 56, 31, 61, 16, 97, 173, 179, 86, 202, 247, 23, 171, 78, 152, 235, 251, 197, 59, 18, 158, 67, 183, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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