← previous blocknext block →recent activity
Analyzing
Block #104,024,800
10 transactions · 10 stateful · 2026-09-11 23:20:35 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,024,800 · 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
2w05w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5468852…a6ef
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x08d3fac0…230a
0x34b655…2a6f
2 touches
0 conflicts
0x0a7577f3…312c
0x34b655…2a6f
2 touches
0 conflicts
0x1f9e985c…c12f
0x34b655…2a6f
2 touches
0 conflicts
0x38c094c2…a251
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 0xc54688527a…dba6ef
Audit this contract →
← previous block·next block →recent activity