Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5540613277c1aab7564cac56699c0589b58e6f58543f111a3efe09a23282a69d

Tx prefix hash: d392332f9991c7f295123a1f403bef3c8811f1489046e15c609606cef22ca1d4
Tx public key: 0046625ed5a304b5c96e1df6d7ffe3a3dbe86604bad0af1b3e88a914b47f6fea
Timestamp: 1694716742 Timestamp [UCT]: 2023-09-14 18:39:02 Age [y:d:h:m:s]: 01:204:00:37:37
Block: 848127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406909 RingCT/type: yes/0
Extra: 010046625ed5a304b5c96e1df6d7ffe3a3dbe86604bad0af1b3e88a914b47f6fea0211000000024b8f5122000000000000000000

1 output(s) for total of 0.950174200000 dcy

stealth address amount amount idx
00: e9a52a90b7f962bec40ea05cf17b2acb031703679d5934afa6979b2bd2fc4f55 0.950174200000 1301711 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": 848137, "vin": [ { "gen": { "height": 848127 } } ], "vout": [ { "amount": 950174200, "target": { "key": "e9a52a90b7f962bec40ea05cf17b2acb031703679d5934afa6979b2bd2fc4f55" } } ], "extra": [ 1, 0, 70, 98, 94, 213, 163, 4, 181, 201, 110, 29, 246, 215, 255, 227, 163, 219, 232, 102, 4, 186, 208, 175, 27, 62, 136, 169, 20, 180, 127, 111, 234, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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