Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad03582cb6dba9136b9c69c9670cc5c77c00bd80c55f57fcbbb4efc33a91ad9c

Tx prefix hash: 1764a50b0f585e8efb649341316e5bfbb3123cca3e4d672c633c89920c73b156
Tx public key: f8ddabf80f75c76996535c1d728303667277e64fb442cd330f419b4c54d652b8
Timestamp: 1697084314 Timestamp [UCT]: 2023-10-12 04:18:34 Age [y:d:h:m:s]: 01:177:18:32:47
Block: 867779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388066 RingCT/type: yes/0
Extra: 01f8ddabf80f75c76996535c1d728303667277e64fb442cd330f419b4c54d652b80211000000094b8f5122000000000000000000

1 output(s) for total of 0.817876955000 dcy

stealth address amount amount idx
00: 3f5bf18ae0bb83d5d7568a6109a6c018eba8396a5eda2505dcfcb0733567b42e 0.817876955000 1322495 of 0

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": 867789, "vin": [ { "gen": { "height": 867779 } } ], "vout": [ { "amount": 817876955, "target": { "key": "3f5bf18ae0bb83d5d7568a6109a6c018eba8396a5eda2505dcfcb0733567b42e" } } ], "extra": [ 1, 248, 221, 171, 248, 15, 117, 199, 105, 150, 83, 92, 29, 114, 131, 3, 102, 114, 119, 230, 79, 180, 66, 205, 51, 15, 65, 155, 76, 84, 214, 82, 184, 2, 17, 0, 0, 0, 9, 75, 143, 81, 34, 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