← previous blocknext block →recent activity
Analyzing
Block #104,196,285
13 transactions · 11 stateful · 2026-09-12 13:52:34 UTC
Parallelism
62/100
Blocked
45%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,196,285 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5666db7d…5dc4
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xf4350838…fa7c
0x34b655…2a6f
8 touches
6 conflicts
0xc425407b…0ec9
0x34b655…2a6f
8 touches
6 conflicts
0xf5f815e7…c83e
0x34b655…2a6f
6 touches
3 conflicts
0x6636a104…d595
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x5666db7d94…495dc4
Audit this contract →
← previous block·next block →recent activity