← previous blocknext block →recent activity
Analyzing
Block #91,977,612
19 transactions · 16 stateful · 2026-07-31 17:38:19 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,977,612 · 19 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
1w02w13w18w110w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f41aff2…ea0a
0x34b655…2a6f
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0xa5a8ffca…8de2
0x34b655…2a6f
4 touches
1 conflict
0x9ea5c5d8…6814
0x34b655…2a6f
4 touches
1 conflict
0x9ea5c5d8…6813
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x5adda4a7…b840
0x34b655…2a6f
4 touches
1 conflict
0xf56b2cc9…3d15
0xd32edf…ff58
3 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 0x4f41aff204…9bea0a
Audit this contract →
← previous block·next block →recent activity