Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25c003f0fcc46c61c97ec7e3e0a8f8422ab48166a2028f1ed4631772205b765c

Tx prefix hash: 2d0962e65ff21b0ec8682a38c13f4586ab6054fbf522fab376f0d09e357c3b3f
Tx public key: eb98d1f2ac9a2f2941a5c44d28b91e04386745427d31f4e5e842e7a7e5309f2c
Timestamp: 1657386341 Timestamp [UCT]: 2022-07-09 17:05:41 Age [y:d:h:m:s]: 02:310:02:43:27
Block: 540162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742801 RingCT/type: yes/0
Extra: 01eb98d1f2ac9a2f2941a5c44d28b91e04386745427d31f4e5e842e7a7e5309f2c021100000007faf35c9c000000000000000000

1 output(s) for total of 9.959079719000 dcy

stealth address amount amount idx
00: 9c483dfbacd181d6558307bd46344bce9b85892451eedd13e513efde9ad527d9 9.959079719000 970367 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": 540172, "vin": [ { "gen": { "height": 540162 } } ], "vout": [ { "amount": 9959079719, "target": { "key": "9c483dfbacd181d6558307bd46344bce9b85892451eedd13e513efde9ad527d9" } } ], "extra": [ 1, 235, 152, 209, 242, 172, 154, 47, 41, 65, 165, 196, 77, 40, 185, 30, 4, 56, 103, 69, 66, 125, 49, 244, 229, 232, 66, 231, 167, 229, 48, 159, 44, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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