Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 330662853fbc149fa2ec6169e7a84335fced21433be490102d558eb21617386b

Tx prefix hash: 967a682e0d216b67fe9f60da57345a4af499636db86abf852bf1bea07cf74c67
Tx public key: b6f1dc7f531f1b68063d4c251b815f37391db54260d28d944954a71ecbbcc71a
Timestamp: 1698365631 Timestamp [UCT]: 2023-10-27 00:13:51 Age [y:d:h:m:s]: 01:156:07:15:14
Block: 878416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372693 RingCT/type: yes/0
Extra: 01b6f1dc7f531f1b68063d4c251b815f37391db54260d28d944954a71ecbbcc71a0211000000034b8f5122000000000000000000

1 output(s) for total of 0.754124689000 dcy

stealth address amount amount idx
00: 9702bd4650ce8c55a4674f2f17d3131c8c47cd4e4857fd2be192e94d4eef2b4e 0.754124689000 1333858 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": 878426, "vin": [ { "gen": { "height": 878416 } } ], "vout": [ { "amount": 754124689, "target": { "key": "9702bd4650ce8c55a4674f2f17d3131c8c47cd4e4857fd2be192e94d4eef2b4e" } } ], "extra": [ 1, 182, 241, 220, 127, 83, 31, 27, 104, 6, 61, 76, 37, 27, 129, 95, 55, 57, 29, 181, 66, 96, 210, 141, 148, 73, 84, 167, 30, 203, 188, 199, 26, 2, 17, 0, 0, 0, 3, 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