Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 291e5ce8a04abe4e69a9c01ae7de6a38ae0667c348a28aa31c0941197c804d14

Tx prefix hash: 96c3e581ca4af3370d10c91b1a55d2dc3c959142c9be96465fdda990e6414db5
Tx public key: 3f8974b37f238878d3f8ed8af42f9f762365c4dca182161243792482de64e853
Timestamp: 1608233198 Timestamp [UCT]: 2020-12-17 19:26:38 Age [y:d:h:m:s]: 04:145:17:05:37
Block: 164034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116560 RingCT/type: yes/0
Extra: 013f8974b37f238878d3f8ed8af42f9f762365c4dca182161243792482de64e8530211000002044ea414e5000000000000000000

1 output(s) for total of 175.592383000000 dcy

stealth address amount amount idx
00: 7493adbadf523c29af063334aece31af8637bc42e0bc9e03174f53ab18f2a02c 175.592383000000 295811 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": 164044, "vin": [ { "gen": { "height": 164034 } } ], "vout": [ { "amount": 175592383000, "target": { "key": "7493adbadf523c29af063334aece31af8637bc42e0bc9e03174f53ab18f2a02c" } } ], "extra": [ 1, 63, 137, 116, 179, 127, 35, 136, 120, 211, 248, 237, 138, 244, 47, 159, 118, 35, 101, 196, 220, 161, 130, 22, 18, 67, 121, 36, 130, 222, 100, 232, 83, 2, 17, 0, 0, 2, 4, 78, 164, 20, 229, 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