← previous blocknext block →recent activity
Analyzing
Block #83,666,740
46 transactions · 33 stateful · 2026-06-25 19:51:31 UTC
Parallelism
70/100
Blocked
64%
Avg conflicts / tx
2.28
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,666,740 · 46 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w09w118w019w121w022w123w224w325w426w527w628w729w830w931w1032w1133w1234w1338w244w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
28 touches
91 conflicts
0x3cf50d44…961b
0x34b655…2a6f
14 touches
21 conflicts
0x3e776e71…4bbf
0x34b655…2a6f
14 touches
21 conflicts
0xb7a3240c…dd63
0x34b655…2a6f
14 touches
21 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x1c48b3ac…a03c
0x34b655…2a6f
8 touches
6 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
91 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity