← previous blocknext block →recent activity
Analyzing
Block #83,667,236
24 transactions · 24 stateful · 2026-06-25 19:54:50 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,667,236 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w18w09w110w211w312w415w018w120w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x925c118c…a1d8
0x34b655…2a6f
8 touches
6 conflicts
0xdf37a93d…879b
0x34b655…2a6f
8 touches
6 conflicts
0x79e62da8…efdc
0x34b655…2a6f
4 touches
1 conflict
0x98d3fc79…df78
0x34b655…2a6f
4 touches
1 conflict
0xbc84980d…5af9
0x34b655…2a6f
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity