← previous blocknext block →recent activity
Analyzing
Block #93,352,670
14 transactions · 13 stateful · 2026-08-05 12:56:52 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,352,670 · 14 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
4w05w17w110w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1a4179d3…0f26
0x068f22…7908
2 touches
0 conflicts
0xf0cb663a…2ebe
0x09475a…400f
2 touches
0 conflicts
0x5eed8370…d27c
0x754704…b603
2 touches
0 conflicts
0x71db4594…0e0c
0x754704…b603
2 touches
0 conflicts
0x00000000…000b
0x78999c…f371
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
3 conflicts on slot 0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block·next block →recent activity