← previous blocknext block →recent activity
Analyzing
Block #93,374,371
14 transactions · 14 stateful · 2026-08-05 14:45:59 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,374,371 · 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
2w03w04w05w16w27w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef50353e…6adc
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x231ccc13…a7c6
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3a51d8ed…0c97
0x34b655…2a6f
2 touches
0 conflicts
0x66473027…6780
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
3 conflicts on slot 0xef50353e89…df6adc
Audit this contract →
← previous block·next block →recent activity