Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c6d7108e0c0c0a0c207c1187a28b0d6970e6bbaa72082748ac8fa9c2bb93d2a

Tx prefix hash: 154343b6935d93c696f80b3a04e225315ca6199f79e91a4c308f42005dd0d796
Tx public key: 9c1413e9b7e995b742274d67ccad6b0929182a0b7701a9661f44f69b53612ecd
Timestamp: 1581823166 Timestamp [UCT]: 2020-02-16 03:19:26 Age [y:d:h:m:s]: 05:018:00:46:27
Block: 65876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1165821 RingCT/type: yes/0
Extra: 019c1413e9b7e995b742274d67ccad6b0929182a0b7701a9661f44f69b53612ecd02110000000312c4732d000000000000000000

1 output(s) for total of 371.328003723000 dcy

stealth address amount amount idx
00: 820cffbfa2178aa0d0f16d1a148d80e09e3f1eb66686b342f0bfc5009e2d67c8 371.328003723000 121493 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": 65886, "vin": [ { "gen": { "height": 65876 } } ], "vout": [ { "amount": 371328003723, "target": { "key": "820cffbfa2178aa0d0f16d1a148d80e09e3f1eb66686b342f0bfc5009e2d67c8" } } ], "extra": [ 1, 156, 20, 19, 233, 183, 233, 149, 183, 66, 39, 77, 103, 204, 173, 107, 9, 41, 24, 42, 11, 119, 1, 169, 102, 31, 68, 246, 155, 83, 97, 46, 205, 2, 17, 0, 0, 0, 3, 18, 196, 115, 45, 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