← previous blocknext block →recent activity
Analyzing
Block #93,347,524
23 transactions · 22 stateful · 2026-08-05 12:31:00 UTC
Parallelism
78/100
Blocked
32%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,347,524 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w08w19w211w214w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41f1e2e5…2edf
0x34b655…2a6f
6 touches
3 conflicts
0xf219f7cf…7379
0xa6afd3…d132
4 touches
1 conflict
0x231ccc13…a7c6
0x34b655…2a6f
4 touches
1 conflict
0x808129fc…f97d
0x34b655…2a6f
4 touches
1 conflict
0xa6389d47…9a28
0x34b655…2a6f
4 touches
1 conflict
0xac8a5059…fd42
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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 0x41f1e2e549…5e2edf
Audit this contract →
← previous block·next block →recent activity