Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c17f5c056a481ee40bcf201ada539a89d725fb22168ce1ff55df85f885225e18

Tx prefix hash: a92e3e0a8c5dfe4f0bb2994776c11c8b30928162ab3d4d85f4dae96601ffb2ce
Tx public key: 522f30c4d336f48fa501655407b433a3a5fda4afd6a42cb2623e9d0b12c2d468
Timestamp: 1684335728 Timestamp [UCT]: 2023-05-17 15:02:08 Age [y:d:h:m:s]: 01:349:14:27:09
Block: 762128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511088 RingCT/type: yes/0
Extra: 01522f30c4d336f48fa501655407b433a3a5fda4afd6a42cb2623e9d0b12c2d468021100000009e6d27f9c000000000000000000

1 output(s) for total of 1.831275761000 dcy

stealth address amount amount idx
00: 344dd4a7b4606e35d6f6a11999f6b4e84cc52e95517a13e4c634514d8eb8d394 1.831275761000 1210847 of 0

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": 762138, "vin": [ { "gen": { "height": 762128 } } ], "vout": [ { "amount": 1831275761, "target": { "key": "344dd4a7b4606e35d6f6a11999f6b4e84cc52e95517a13e4c634514d8eb8d394" } } ], "extra": [ 1, 82, 47, 48, 196, 211, 54, 244, 143, 165, 1, 101, 84, 7, 180, 51, 163, 165, 253, 164, 175, 214, 164, 44, 178, 98, 62, 157, 11, 18, 194, 212, 104, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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