Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc400a429c665615c2f373a911859b2b4fcd215887d16d4e47a848380c611a53

Tx prefix hash: 23b356cc1c02531397c60d552942cab2101b4522f8895fcce4a14f4269e271c3
Tx public key: 019798af7f6028fab24203f58d540e5e5079e9fbdec2a133e2fe40b222c33d5b
Timestamp: 1576109032 Timestamp [UCT]: 2019-12-12 00:03:52 Age [y:d:h:m:s]: 05:325:01:08:02
Block: 25706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1375892 RingCT/type: yes/0
Extra: 01019798af7f6028fab24203f58d540e5e5079e9fbdec2a133e2fe40b222c33d5b021100000009ad433a0b000000000000000000

1 output(s) for total of 504.459400583000 dcy

stealth address amount amount idx
00: 3141d73355210b27d64ed51860afc1747cfa40e6327aa89f1c1942254db30b50 504.459400583000 42445 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": 25716, "vin": [ { "gen": { "height": 25706 } } ], "vout": [ { "amount": 504459400583, "target": { "key": "3141d73355210b27d64ed51860afc1747cfa40e6327aa89f1c1942254db30b50" } } ], "extra": [ 1, 1, 151, 152, 175, 127, 96, 40, 250, 178, 66, 3, 245, 141, 84, 14, 94, 80, 121, 233, 251, 222, 194, 161, 51, 226, 254, 64, 178, 34, 195, 61, 91, 2, 17, 0, 0, 0, 9, 173, 67, 58, 11, 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