Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc94af3f024c5af96686e9c44f0bc3f5b5341ce41cdde5fdcb16f84b746efe10

Tx prefix hash: bf9f12944f14c7e15f3a778cedf8f03ebf5b8fb06045ba684c4b53a5e5aa6d89
Tx public key: 885071e6e670deca08a315e05fe1d7ed066ba9dd7bcb77ad97a4bfc830af25b1
Timestamp: 1693955792 Timestamp [UCT]: 2023-09-05 23:16:32 Age [y:d:h:m:s]: 01:133:01:57:18
Block: 841817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356445 RingCT/type: yes/0
Extra: 01885071e6e670deca08a315e05fe1d7ed066ba9dd7bcb77ad97a4bfc830af25b10211000000024b8f5122000000000000000000

1 output(s) for total of 0.997036122000 dcy

stealth address amount amount idx
00: adae52aea42e21c328f617d19c135f99b45b9cc83bc71c008dfa32bcaedfa2f7 0.997036122000 1294885 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": 841827, "vin": [ { "gen": { "height": 841817 } } ], "vout": [ { "amount": 997036122, "target": { "key": "adae52aea42e21c328f617d19c135f99b45b9cc83bc71c008dfa32bcaedfa2f7" } } ], "extra": [ 1, 136, 80, 113, 230, 230, 112, 222, 202, 8, 163, 21, 224, 95, 225, 215, 237, 6, 107, 169, 221, 123, 203, 119, 173, 151, 164, 191, 200, 48, 175, 37, 177, 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