Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48491e12de3a0fc4c1c58bb29247ebea69f6eb74f9c21db098284ce58563e311

Tx prefix hash: 71a267abc301dfa5f2088828e3b245d6d16c14906df5816fe3d5a8cfd96f84b3
Tx public key: 25d97d46751d11c267ce592c15a795ab5757487893184ea2aa474bfdc0f728ae
Timestamp: 1634500793 Timestamp [UCT]: 2021-10-17 19:59:53 Age [y:d:h:m:s]: 03:108:07:48:40
Block: 355127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 855106 RingCT/type: yes/0
Extra: 0125d97d46751d11c267ce592c15a795ab5757487893184ea2aa474bfdc0f728ae02110000004cf29d7abf000000000000000000

1 output(s) for total of 40.861776578000 dcy

stealth address amount amount idx
00: 0003f887ace3aec685002de0ecc46ddde6f12a23b7085e057c5942fdaaa2326c 40.861776578000 725151 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": 355137, "vin": [ { "gen": { "height": 355127 } } ], "vout": [ { "amount": 40861776578, "target": { "key": "0003f887ace3aec685002de0ecc46ddde6f12a23b7085e057c5942fdaaa2326c" } } ], "extra": [ 1, 37, 217, 125, 70, 117, 29, 17, 194, 103, 206, 89, 44, 21, 167, 149, 171, 87, 87, 72, 120, 147, 24, 78, 162, 170, 71, 75, 253, 192, 247, 40, 174, 2, 17, 0, 0, 0, 76, 242, 157, 122, 191, 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