Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bed4a9b1ee27c389d9b3d195feb00f77d26964f401a8ea4ca745d8462df1fe83

Tx prefix hash: 832f368a49d238c0dcb3b400572bec8f89394b992994561b77e27f8f11d26255
Tx public key: be8386ce344590f1a2b953b7a045245561d9baa7f6d8ef080505874148075dee
Timestamp: 1672662673 Timestamp [UCT]: 2023-01-02 12:31:13 Age [y:d:h:m:s]: 02:106:18:14:25
Block: 665973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597991 RingCT/type: yes/0
Extra: 01be8386ce344590f1a2b953b7a045245561d9baa7f6d8ef080505874148075dee02110000000152542ceb000000000000000000

1 output(s) for total of 3.813774017000 dcy

stealth address amount amount idx
00: 9bdc3f0fd7c9047718a7a75acb4c9d9629637f2eb9482c3674f80c2898258f0d 3.813774017000 1107046 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": 665983, "vin": [ { "gen": { "height": 665973 } } ], "vout": [ { "amount": 3813774017, "target": { "key": "9bdc3f0fd7c9047718a7a75acb4c9d9629637f2eb9482c3674f80c2898258f0d" } } ], "extra": [ 1, 190, 131, 134, 206, 52, 69, 144, 241, 162, 185, 83, 183, 160, 69, 36, 85, 97, 217, 186, 167, 246, 216, 239, 8, 5, 5, 135, 65, 72, 7, 93, 238, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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