← previous blocknext block →recent activity
Analyzing
Block #93,406,511
12 transactions · 9 stateful · 2026-08-05 17:27:35 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,406,511 · 12 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
5w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xdf1bda53…644d
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x2d7fe5a5…4bbc
0x91b81b…6d56
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
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 0x4e8c4408ae…50d37b
Audit this contract →
← previous block·next block →recent activity