← previous blocknext block →recent activity
Analyzing
Block #91,017,027
16 transactions · 15 stateful · 2026-07-28 09:03:29 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,017,027 · 16 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
4w05w19w214w015w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98b8e5ef…bda4
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x363f99e4…32c8
0x34b655…2a6f
4 touches
1 conflict
0x5c56b0af…a9df
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x85d4c7be…173a
0x34b655…2a6f
4 touches
1 conflict
0xa535ecc7…c0e0
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 0x98b8e5ef76…3fbda4
Audit this contract →
← previous block·next block →recent activity