Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20d981ce33265b48ddb300d4b9e7b16833ce97c97bf7b0fa6301111229a7efdd

Tx prefix hash: 0199cd7b267d628b6ba0503fa6a44e79d8683f43700162bde0684a33fe75ef8e
Tx public key: 7c987ef67a59f8a9d0c1a503573ed97106d9db592256de9c86f4c7d95f99c6a4
Timestamp: 1734559023 Timestamp [UCT]: 2024-12-18 21:57:03 Age [y:d:h:m:s]: 00:174:07:40:18
Block: 1178167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124380 RingCT/type: yes/0
Extra: 017c987ef67a59f8a9d0c1a503573ed97106d9db592256de9c86f4c7d95f99c6a40211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 614c525b7569d65adc9ea3913983a17d32821062b2d2e238bd9ab8656e0d819d 0.600000000000 1664552 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": 1178177, "vin": [ { "gen": { "height": 1178167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "614c525b7569d65adc9ea3913983a17d32821062b2d2e238bd9ab8656e0d819d" } } ], "extra": [ 1, 124, 152, 126, 246, 122, 89, 248, 169, 208, 193, 165, 3, 87, 62, 217, 113, 6, 217, 219, 89, 34, 86, 222, 156, 134, 244, 199, 217, 95, 153, 198, 164, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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