← previous blocknext block →recent activity
Analyzing
Block #93,322,184
19 transactions · 18 stateful · 2026-08-05 10:23:36 UTC
Parallelism
79/100
Blocked
28%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,322,184 · 19 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
2w05w07w08w111w113w214w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2cb4b4a…b088
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
6 touches
3 conflicts
0x04e17b28…d9f0
0x34b655…2a6f
4 touches
1 conflict
0x055b5b38…8737
0x34b655…2a6f
4 touches
1 conflict
0x11027baf…6ac3
0x34b655…2a6f
4 touches
1 conflict
0x28933b5c…e3c5
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xc2cb4b4ab2…5cb088
Audit this contract →
← previous block·next block →recent activity