Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67e91bf8dae489ca044d587cbc7b0ed8f844a7fe4fa4e20dfbf75f2556eb2941

Tx prefix hash: a90a2d3edd099567b213a45f017749e94e6b721c7ee06065f2bf6c34804a8098
Tx public key: b9e137d0b6adc217ad15e63f5436123567895e03a3b0c38b9203b321e55cc1b4
Timestamp: 1705695614 Timestamp [UCT]: 2024-01-19 20:20:14 Age [y:d:h:m:s]: 01:097:22:50:15
Block: 938935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331135 RingCT/type: yes/0
Extra: 01b9e137d0b6adc217ad15e63f5436123567895e03a3b0c38b9203b321e55cc1b40211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 995f1a229cd3e6d91e1edf4c95e50c953ac9ee22f419a3de74f7c7139198b908 0.600000000000 1397017 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": 938945, "vin": [ { "gen": { "height": 938935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "995f1a229cd3e6d91e1edf4c95e50c953ac9ee22f419a3de74f7c7139198b908" } } ], "extra": [ 1, 185, 225, 55, 208, 182, 173, 194, 23, 173, 21, 230, 63, 84, 54, 18, 53, 103, 137, 94, 3, 163, 176, 195, 139, 146, 3, 179, 33, 229, 92, 193, 180, 2, 17, 0, 0, 0, 4, 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