← previous blocknext block →recent activity
Analyzing
Block #104,166,290
22 transactions · 21 stateful · 2026-09-12 11:20:26 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,166,290 · 22 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
1w02w14w05w06w111w112w213w314w416w519w620w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7b9eede…2538
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd1448207…452d
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
6 touches
3 conflicts
0xd18e4cb7…88d4
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x42522e76…2592
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
21 conflicts on slot 0xe7b9eedee8…f62538
Audit this contract →
← previous block·next block →recent activity