← previous blocknext block →recent activity
Analyzing
Block #83,628,409
8 transactions · 6 stateful · 2026-06-25 15:35:44 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,628,409 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x90fefe5e…f0c6
0x34b655…2a6f
4 touches
1 conflict
0x2cb897e4…21ea
0x34b655…2a6f
4 touches
1 conflict
0xb4de1149…6546
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x1500b8e2…5486
0x34b655…2a6f
2 touches
0 conflicts
0x1bbe8b33…dc64
0x34b655…2a6f
2 touches
0 conflicts
0x1fe92c2a…cbb1
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity