← previous blocknext block →recent activity
Analyzing
Block #104,167,332
27 transactions · 26 stateful · 2026-09-12 11:25:42 UTC
Parallelism
78/100
Blocked
27%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,167,332 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w110w111w213w314w416w517w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x9b44dbae…6602
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x5fde4971…aac9
0x34b655…2a6f
6 touches
3 conflicts
0x9a6bc012…7495
0x34b655…2a6f
6 touches
3 conflicts
0x77498c8d…5665
0x34b655…2a6f
6 touches
3 conflicts
0x3accf018…2e8b
0x34b655…2a6f
6 touches
3 conflicts
0xabb9f292…17a3
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity