Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a3db3150c79c58fb2a0e44ca58befee0b6829a4c1b7f269490cbc6bb6863a66

Tx prefix hash: 628f7fbffd09a86650a40187114104578ce292d7816575293724e1ec1d07a1fa
Tx public key: 46a503aee6f775b305429e6897676aa70e22e8703d37d5fedcab6a4b4bbad26f
Timestamp: 1684638577 Timestamp [UCT]: 2023-05-21 03:09:37 Age [y:d:h:m:s]: 01:196:14:34:59
Block: 764645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401928 RingCT/type: yes/0
Extra: 0146a503aee6f775b305429e6897676aa70e22e8703d37d5fedcab6a4b4bbad26f021100000003b3164c24000000000000000000

1 output(s) for total of 1.796444802000 dcy

stealth address amount amount idx
00: 3b53b93ad4579b6c0269d072a4156c8fe73baf1917a107a11307d17cfec01bbc 1.796444802000 1213588 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": 764655, "vin": [ { "gen": { "height": 764645 } } ], "vout": [ { "amount": 1796444802, "target": { "key": "3b53b93ad4579b6c0269d072a4156c8fe73baf1917a107a11307d17cfec01bbc" } } ], "extra": [ 1, 70, 165, 3, 174, 230, 247, 117, 179, 5, 66, 158, 104, 151, 103, 106, 167, 14, 34, 232, 112, 61, 55, 213, 254, 220, 171, 106, 75, 75, 186, 210, 111, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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