← previous blocknext block →recent activity
Analyzing
Block #93,366,544
10 transactions · 9 stateful · 2026-08-05 14:06:38 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,366,544 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e9a3afd…a6e5
0x34b655…2a6f
4 touches
1 conflict
0x0aeef2b4…12cf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0c7441d3…34fc
0x34b655…2a6f
2 touches
0 conflicts
0x2e5db601…32e5
0x34b655…2a6f
2 touches
0 conflicts
0x3ff58865…cdd3
0x34b655…2a6f
2 touches
0 conflicts
0x45321d59…fc8a
0x34b655…2a6f
2 touches
0 conflicts
0x480463fd…bd45
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x1e9a3afdd5…2da6e5
Audit this contract →
← previous block·next block →recent activity