Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a59326219d887feb4321a7a397b009fbaf7001bc722277e306f58acdf6ffac7c

Tx prefix hash: f41e7bb5c56166e89f8a0fde098b25d43d0de60c55af34c86ad88851b0a22b60
Tx public key: ead692c14e3385e8655d968dd23ac7cc1e6d579df3139fcd58c52901feecb34b
Timestamp: 1707853743 Timestamp [UCT]: 2024-02-13 19:49:03 Age [y:d:h:m:s]: 01:057:06:12:07
Block: 956853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301963 RingCT/type: yes/0
Extra: 01ead692c14e3385e8655d968dd23ac7cc1e6d579df3139fcd58c52901feecb34b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1b8ca595d2815b0c576b9887255dd2e67d05995061cdda6b9b57e45e11a8750 0.600000000000 1416165 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": 956863, "vin": [ { "gen": { "height": 956853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1b8ca595d2815b0c576b9887255dd2e67d05995061cdda6b9b57e45e11a8750" } } ], "extra": [ 1, 234, 214, 146, 193, 78, 51, 133, 232, 101, 93, 150, 141, 210, 58, 199, 204, 30, 109, 87, 157, 243, 19, 159, 205, 88, 197, 41, 1, 254, 236, 179, 75, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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