← previous blocknext block →recent activity
Analyzing
Block #93,186,686
14 transactions · 10 stateful · 2026-08-04 23:02:21 UTC
Parallelism
71/100
Blocked
30%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,186,686 · 14 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
7w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd8bc53a3…c2fe
0x34b655…2a6f
4 touches
1 conflict
0x0e0a3c1a…f9fb
0x34b655…2a6f
4 touches
1 conflict
0x77f5ee28…347d
0x34b655…2a6f
4 touches
1 conflict
0x9c74586a…b008
0x34b655…2a6f
4 touches
1 conflict
0x9d20b779…6b98
0x34b655…2a6f
4 touches
1 conflict
0xc467a38b…cf75
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity