← previous blocknext block →recent activity
Analyzing
Block #104,192,172
36 transactions · 28 stateful · 2026-09-12 13:31:36 UTC
Parallelism
75/100
Blocked
54%
Avg conflicts / tx
1.14
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #104,192,172 · 36 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w110w218w325w426w527w228w629w130w231w334w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
6 touches
3 conflicts
0x344dd398…b320
0x34b655…2a6f
6 touches
3 conflicts
0xa2869417…b1cb
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity