← previous blocknext block →recent activity
Analyzing
Block #91,274,071
12 transactions · 12 stateful · 2026-07-29 06:37:30 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,274,071 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x03d53e11…3f6f
0x34b655…2a6f
2 touches
0 conflicts
0x0e5d4ac2…a471
0x34b655…2a6f
2 touches
0 conflicts
0x28c62bca…b746
0x34b655…2a6f
2 touches
0 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
2 touches
0 conflicts
0x7cb2f3fa…4836
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 0xc0eb79d1cb…5529a4
Audit this contract →
← previous block·next block →recent activity