← previous blocknext block →recent activity
Analyzing
Block #83,401,909
18 transactions · 15 stateful · 2026-06-24 14:24:01 UTC
Parallelism
72/100
Blocked
40%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,401,909 · 18 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
1w03w04w17w09w111w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0ad4dbe8…ae93
0x34b655…2a6f
4 touches
1 conflict
0x124be23b…2cca
0x34b655…2a6f
4 touches
1 conflict
0x4efb974a…6126
0x34b655…2a6f
4 touches
1 conflict
0x58b9951c…1885
0x34b655…2a6f
4 touches
1 conflict
0x7425a853…a582
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity