Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00be3a90d5384ecefea057ba10b04eae65077eab5bdb74487a98be230ee90e08

Tx prefix hash: 65b785bb2e8bf5fd1923de95ac1160e95b2559c19d7171daf67b0c075d3fed47
Tx public key: 3f5a166566ae12143be0b3d0838fd382ed585a4ebe8fedae25b932874f2d3ba6
Timestamp: 1712514892 Timestamp [UCT]: 2024-04-07 18:34:52 Age [y:d:h:m:s]: 01:065:15:54:24
Block: 995468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307922 RingCT/type: yes/0
Extra: 013f5a166566ae12143be0b3d0838fd382ed585a4ebe8fedae25b932874f2d3ba602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e95c039cac8af33529ead7e6f671b44ad10d1783f69fbed3de0b928ec362a0b5 0.600000000000 1455876 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": 995478, "vin": [ { "gen": { "height": 995468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e95c039cac8af33529ead7e6f671b44ad10d1783f69fbed3de0b928ec362a0b5" } } ], "extra": [ 1, 63, 90, 22, 101, 102, 174, 18, 20, 59, 224, 179, 208, 131, 143, 211, 130, 237, 88, 90, 78, 190, 143, 237, 174, 37, 185, 50, 135, 79, 45, 59, 166, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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