Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1ecd5d257877a538d4964927882b291fb4a9116187825784047cd606b44057b

Tx prefix hash: 378ee7dad549d4fdf690b965489aba6c175cb95bf6e531baf62533ada564b953
Tx public key: 381d39197f0a9eb962a6213605229ccd5b14f06e12a6c5bca90e4ed632e01d1f
Timestamp: 1582109520 Timestamp [UCT]: 2020-02-19 10:52:00 Age [y:d:h:m:s]: 05:014:21:12:07
Block: 68085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1163737 RingCT/type: yes/0
Extra: 01381d39197f0a9eb962a6213605229ccd5b14f06e12a6c5bca90e4ed632e01d1f02110000000ad81c26c0000000000000000000

1 output(s) for total of 365.095885015000 dcy

stealth address amount amount idx
00: 7d0fc2ebf271c2aa1fafe430e11ed266c2e86cb0556748145894abe6f3d9e38b 365.095885015000 125451 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": 68095, "vin": [ { "gen": { "height": 68085 } } ], "vout": [ { "amount": 365095885015, "target": { "key": "7d0fc2ebf271c2aa1fafe430e11ed266c2e86cb0556748145894abe6f3d9e38b" } } ], "extra": [ 1, 56, 29, 57, 25, 127, 10, 158, 185, 98, 166, 33, 54, 5, 34, 156, 205, 91, 20, 240, 110, 18, 166, 197, 188, 169, 14, 78, 214, 50, 224, 29, 31, 2, 17, 0, 0, 0, 10, 216, 28, 38, 192, 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