← previous blocknext block →recent activity
Analyzing
Block #93,371,452
20 transactions · 19 stateful · 2026-08-05 14:31:19 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,371,452 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w18w19w110w211w213w316w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x861e5aef…d32c
0x34b655…2a6f
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x1803586e…d149
0xa6afd3…d132
6 touches
3 conflicts
0x1a287886…0266
0xa6afd3…d132
6 touches
3 conflicts
0xdfc21d7c…e062
0x34b655…2a6f
4 touches
1 conflict
0xe31e77c9…75d6
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
3 conflicts on slot 0x861e5aeffa…5cd32c
Audit this contract →
← previous block·next block →recent activity