Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab51ce06df996108dee3c17ca20d47580104b724887b52a9ac1792eab3c178ea

Tx prefix hash: 02cf821d19e547c47427516d84850ad1201e6cb9ef44913bd7638a34ae62e665
Tx public key: 94b6b24e8540e3ca5d5a40c1e8442f30f8939f3f1c6270e87632a731ae493bc8
Timestamp: 1737535138 Timestamp [UCT]: 2025-01-22 08:38:58 Age [y:d:h:m:s]: 00:147:16:05:36
Block: 1202735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105273 RingCT/type: yes/0
Extra: 0194b6b24e8540e3ca5d5a40c1e8442f30f8939f3f1c6270e87632a731ae493bc802110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65431029723f2255b11c692730775771b92989946784b7b74e0a8885284cc9a1 0.600000000000 1689400 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": 1202745, "vin": [ { "gen": { "height": 1202735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65431029723f2255b11c692730775771b92989946784b7b74e0a8885284cc9a1" } } ], "extra": [ 1, 148, 182, 178, 78, 133, 64, 227, 202, 93, 90, 64, 193, 232, 68, 47, 48, 248, 147, 159, 63, 28, 98, 112, 232, 118, 50, 167, 49, 174, 73, 59, 200, 2, 17, 0, 0, 0, 11, 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