← previous blocknext block →recent activity
Analyzing
Block #93,404,364
11 transactions · 9 stateful · 2026-08-05 17:16:47 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,404,364 · 11 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
2w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6000ba5…8d65
0x34b655…2a6f
4 touches
1 conflict
0x94bb14fe…8f47
0x34b655…2a6f
4 touches
1 conflict
0xac8a5059…fd42
0x34b655…2a6f
4 touches
1 conflict
0x07916f42…0bf7
0x34b655…2a6f
4 touches
1 conflict
0x1119ab9e…b631
0x34b655…2a6f
4 touches
1 conflict
0x19b4e3fd…3821
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x41d39318…d624
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 0xc6000ba5c1…988d65
Audit this contract →
← previous block·next block →recent activity