Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 364ee62c58737490cd1e8bda4a3b96ba1f8bc5f57fad5acb7304751d1221576a

Tx prefix hash: c9ad6d5a2da278f9f5d2ef289cbb540bc170841042eb279beba078426b19737e
Tx public key: 41f9b56a6f73b9a9eb9ade550476d930a1936121a34843c46d93b53f7c12d8b4
Timestamp: 1717308719 Timestamp [UCT]: 2024-06-02 06:11:59 Age [y:d:h:m:s]: 00:348:20:23:32
Block: 1035254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249333 RingCT/type: yes/0
Extra: 0141f9b56a6f73b9a9eb9ade550476d930a1936121a34843c46d93b53f7c12d8b402110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf38770d2b58008857c9fc02a5e2372346fc19b7ae5c2f59d6e2e52bd71b450c 0.600000000000 1503775 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": 1035264, "vin": [ { "gen": { "height": 1035254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf38770d2b58008857c9fc02a5e2372346fc19b7ae5c2f59d6e2e52bd71b450c" } } ], "extra": [ 1, 65, 249, 181, 106, 111, 115, 185, 169, 235, 154, 222, 85, 4, 118, 217, 48, 161, 147, 97, 33, 163, 72, 67, 196, 109, 147, 181, 63, 124, 18, 216, 180, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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