Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bba309f18e555a8bdcaa359e1077556b535021e5f6c35e1d69e166b8c43e4db8

Tx prefix hash: d6a30f70c25679716bf6b4005220220a96e64b60889940383cb86ce9ba4d44a0
Tx public key: c2e9e5de6e019713fd3a3ef26e84dd6186dadddcad431533cd07767af72444f4
Timestamp: 1698147237 Timestamp [UCT]: 2023-10-24 11:33:57 Age [y:d:h:m:s]: 02:014:13:44:05
Block: 876592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529996 RingCT/type: yes/0
Extra: 01c2e9e5de6e019713fd3a3ef26e84dd6186dadddcad431533cd07767af72444f4021100000008faf35c9c000000000000000000

1 output(s) for total of 0.764692501000 dcy

stealth address amount amount idx
00: 60af1abfedc1c88dca29085b1a22d1d5da73a2e9c2a19de69cf4249da0eaa9e5 0.764692501000 1331922 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": 876602, "vin": [ { "gen": { "height": 876592 } } ], "vout": [ { "amount": 764692501, "target": { "key": "60af1abfedc1c88dca29085b1a22d1d5da73a2e9c2a19de69cf4249da0eaa9e5" } } ], "extra": [ 1, 194, 233, 229, 222, 110, 1, 151, 19, 253, 58, 62, 242, 110, 132, 221, 97, 134, 218, 221, 220, 173, 67, 21, 51, 205, 7, 118, 122, 247, 36, 68, 244, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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