Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76813394b02682b00110a7f70f618240f4e1f30bd6ba360e80191f1fa845d069

Tx prefix hash: bb92d953ea54482aa0511f4846ecdd0da61979f1bcad3620916143c76c51e87a
Tx public key: 10e82ed7bfd6fcb964a6ed27503c89fec5e59d2597dc7194f79db33c16ae36d8
Timestamp: 1738198066 Timestamp [UCT]: 2025-01-30 00:47:46 Age [y:d:h:m:s]: 00:137:10:47:06
Block: 1208005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98204 RingCT/type: yes/0
Extra: 0110e82ed7bfd6fcb964a6ed27503c89fec5e59d2597dc7194f79db33c16ae36d8021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b90965e96c85dbc99eb8f45c4cdbdf6e62c61ef84a676fd10b260c68fa51751 0.600000000000 1694732 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": 1208015, "vin": [ { "gen": { "height": 1208005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b90965e96c85dbc99eb8f45c4cdbdf6e62c61ef84a676fd10b260c68fa51751" } } ], "extra": [ 1, 16, 232, 46, 215, 191, 214, 252, 185, 100, 166, 237, 39, 80, 60, 137, 254, 197, 229, 157, 37, 151, 220, 113, 148, 247, 157, 179, 60, 22, 174, 54, 216, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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