← previous blocknext block →recent activity
Analyzing
Block #91,147,658
18 transactions · 16 stateful · 2026-07-28 20:00:48 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,147,658 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w17w110w212w213w316w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x006c3b86…59a9
0x34b655…2a6f
4 touches
1 conflict
0x0d2e1791…c1dd
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x332ea34a…a4b6
0x34b655…2a6f
4 touches
1 conflict
0x3e4af36e…07ae
0x34b655…2a6f
4 touches
1 conflict
0x4284bede…72ef
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
1 conflict on slot 0x006c3b8659…7a59a9
Audit this contract →
← previous block·next block →recent activity