← previous blocknext block →recent activity
Analyzing
Block #93,233,199
10 transactions · 7 stateful · 2026-08-05 02:56:12 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,233,199 · 10 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
2w04w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7575128a…8cf9
0x34b655…2a6f
4 touches
1 conflict
0xc7d08bca…e210
0x34b655…2a6f
4 touches
1 conflict
0xe73b93bf…c0e1
0x34b655…2a6f
4 touches
1 conflict
0x0a360aef…2e85
0x34b655…2a6f
2 touches
0 conflicts
0x16f8e14a…f6e4
0x34b655…2a6f
2 touches
0 conflicts
0x1dc9cd60…5cd2
0x34b655…2a6f
2 touches
0 conflicts
0x1ef69984…7076
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
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity