← previous blocknext block →recent activity
Analyzing
Block #91,409,484
19 transactions · 15 stateful · 2026-07-29 17:59:17 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,409,484 · 19 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
2w03w19w010w113w014w115w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dda03d2…fe0d
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xd676e291…3ecf
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
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 0x4dda03d217…48fe0d
Audit this contract →
← previous block·next block →recent activity