← previous blocknext block →recent activity
Analyzing
Block #91,824,317
13 transactions · 12 stateful · 2026-07-31 04:47:06 UTC
Parallelism
62/100
Blocked
58%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,824,317 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w26w39w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c253530…0a48
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x74ba62be…2429
0x34b655…2a6f
8 touches
6 conflicts
0x7506443a…4820
0x34b655…2a6f
6 touches
3 conflicts
0x7e9d81d0…bd7e
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
6 touches
3 conflicts
0x213a54fa…c85f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x0c25353004…980a48
Audit this contract →
← previous block·next block →recent activity