Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb743fdcd264d141a06a85b3c0f22c322f2149b4b55410c3235c492518be23fd

Tx prefix hash: d051cb69d23798c7dc15001bb9ce948c9404a3e96155315cd3ebcba216018072
Tx public key: 830ec895ec0c7cbbbbd7e9101bc580332482141bfeceaf77fea7f28cd3c1fa71
Timestamp: 1583456448 Timestamp [UCT]: 2020-03-06 01:00:48 Age [y:d:h:m:s]: 04:332:01:03:32
Block: 77159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131596 RingCT/type: yes/0
Extra: 01830ec895ec0c7cbbbbd7e9101bc580332482141bfeceaf77fea7f28cd3c1fa710211000000047adf42d3000000000000000000

1 output(s) for total of 340.675574436000 dcy

stealth address amount amount idx
00: 5f92cdb7fcdf7dddd8e2387e8ab4a8c2262315105b320776ada1e7b4f5404c79 340.675574436000 142031 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": 77169, "vin": [ { "gen": { "height": 77159 } } ], "vout": [ { "amount": 340675574436, "target": { "key": "5f92cdb7fcdf7dddd8e2387e8ab4a8c2262315105b320776ada1e7b4f5404c79" } } ], "extra": [ 1, 131, 14, 200, 149, 236, 12, 124, 187, 187, 215, 233, 16, 27, 197, 128, 51, 36, 130, 20, 27, 254, 206, 175, 119, 254, 167, 242, 140, 211, 193, 250, 113, 2, 17, 0, 0, 0, 4, 122, 223, 66, 211, 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