← previous blocknext block →recent activity
Analyzing
Block #91,244,453
26 transactions · 25 stateful · 2026-07-29 04:07:41 UTC
Parallelism
62/100
Blocked
60%
Avg conflicts / tx
1.77
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,244,453 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w38w411w412w515w616w717w118w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5a1b2fe…5369
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xefa65ccf…1078
0x34b655…2a6f
6 touches
3 conflicts
0x5190d7ef…6058
0x34b655…2a6f
6 touches
3 conflicts
0x64a785e4…0110
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
21 conflicts on slot 0xc5a1b2febf…f05369
Audit this contract →
← previous block·next block →recent activity