← previous blocknext block →recent activity
Analyzing
Block #104,149,187
16 transactions · 15 stateful · 2026-09-12 09:53:31 UTC
Parallelism
56/100
Blocked
40%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,149,187 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w110w211w312w413w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x705a9a1a…db08
0x34b655…2a6f
4 touches
1 conflict
0xc87e767e…4bba
0x34b655…2a6f
4 touches
1 conflict
0xf4350838…fa7c
0x34b655…2a6f
4 touches
1 conflict
0x5cc231f5…f1cd
0x34ae4d…3fc5
2 touches
0 conflicts
0xdb067026…9eb8
0x34ae4d…3fc5
2 touches
0 conflicts
0xe2263bea…6a9d
0x34ae4d…3fc5
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity