Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93677db1fb514ba0c2af1a9e60819d250fccc097fa57f6ab35b8675d637d228b

Tx prefix hash: dac1b7fa2c5a9f6be8c2b7552c5d9aa3e1935d2ce104565a46080dbe923b475c
Tx public key: 8fa85d8a6b7f14e4a5461adfa0879929941689a69293a522274c34226e66b719
Timestamp: 1704635767 Timestamp [UCT]: 2024-01-07 13:56:07 Age [y:d:h:m:s]: 01:016:10:05:36
Block: 930159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273038 RingCT/type: yes/0
Extra: 018fa85d8a6b7f14e4a5461adfa0879929941689a69293a522274c34226e66b7190211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 236440c035dd859a7a2398b8f72d57c4bef98a3d5c2aa20aad07077a43818d50 0.600000000000 1388041 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": 930169, "vin": [ { "gen": { "height": 930159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "236440c035dd859a7a2398b8f72d57c4bef98a3d5c2aa20aad07077a43818d50" } } ], "extra": [ 1, 143, 168, 93, 138, 107, 127, 20, 228, 165, 70, 26, 223, 160, 135, 153, 41, 148, 22, 137, 166, 146, 147, 165, 34, 39, 76, 52, 34, 110, 102, 183, 25, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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