← previous blocknext block →recent activity
Analyzing
Block #91,294,812
17 transactions · 16 stateful · 2026-07-29 08:21:55 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,294,812 · 17 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
1w02w16w08w010w011w112w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff3dbbcd…5060
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x1e737223…2278
0x34b655…2a6f
4 touches
1 conflict
0x2f058af7…9d8f
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x44a35e35…6dcf
0x34b655…2a6f
4 touches
1 conflict
0x572fd7e7…dd79
0x34b655…2a6f
4 touches
1 conflict
0x5bb46f6c…7693
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 0xff3dbbcd67…0c5060
Audit this contract →
← previous block·next block →recent activity