← previous blocknext block →recent activity
Analyzing
Block #83,637,055
32 transactions · 20 stateful · 2026-06-25 16:33:30 UTC
Parallelism
81/100
Blocked
55%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,637,055 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w216w117w018w120w121w222w325w428w530w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75cdffd8…c217
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x5a5dd7b4…fba4
0x34b655…2a6f
6 touches
3 conflicts
0x1e1c4638…c7c9
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
4 touches
1 conflict
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
6 conflicts on slot 0x75cdffd8c9…dec217
Audit this contract →
← previous block·next block →recent activity