Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b8b6fe0896e8100e1f8a8b8c164c2674410964fde08116e15d472a7437cf596

Tx prefix hash: af3cd36ff9719bac93850bedd1c68adbcde210c6cfcad2f578e62e86b7726a6e
Tx public key: 58e9c0fedc0bbbb58ea1b7e1b17e9cc907a94687d8cf8768a809115600eb70f7
Timestamp: 1709371386 Timestamp [UCT]: 2024-03-02 09:23:06 Age [y:d:h:m:s]: 01:083:20:45:40
Block: 969443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320985 RingCT/type: yes/0
Extra: 0158e9c0fedc0bbbb58ea1b7e1b17e9cc907a94687d8cf8768a809115600eb70f70211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b837df1e6c46efe4f6c92b7b92bd35c657f314ba3ec75a012701c4dfc8ae231 0.600000000000 1429274 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": 969453, "vin": [ { "gen": { "height": 969443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b837df1e6c46efe4f6c92b7b92bd35c657f314ba3ec75a012701c4dfc8ae231" } } ], "extra": [ 1, 88, 233, 192, 254, 220, 11, 187, 181, 142, 161, 183, 225, 177, 126, 156, 201, 7, 169, 70, 135, 216, 207, 135, 104, 168, 9, 17, 86, 0, 235, 112, 247, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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