Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c5a24f4a76e88bdbab8f2cf8bb63a8dc3d086c9311b70fde9066354c54b8e31

Tx prefix hash: 3a528adcac7235700a4c633ef36702b4d65c25d47c5b85c0751a1c46829451e0
Tx public key: fa18c84f70b84bcb398942ed2fd25f03ec892ef0affc0dd4907ff0b0fba664b3
Timestamp: 1731885633 Timestamp [UCT]: 2024-11-17 23:20:33 Age [y:d:h:m:s]: 00:119:00:20:57
Block: 1156009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84876 RingCT/type: yes/0
Extra: 01fa18c84f70b84bcb398942ed2fd25f03ec892ef0affc0dd4907ff0b0fba664b3021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6292e04e77723eedeed20049e0300ef2f42df231b836f10f24dd3bf40a2674dc 0.600000000000 1641628 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": 1156019, "vin": [ { "gen": { "height": 1156009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6292e04e77723eedeed20049e0300ef2f42df231b836f10f24dd3bf40a2674dc" } } ], "extra": [ 1, 250, 24, 200, 79, 112, 184, 75, 203, 57, 137, 66, 237, 47, 210, 95, 3, 236, 137, 46, 240, 175, 252, 13, 212, 144, 127, 240, 176, 251, 166, 100, 179, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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