← previous blocknext block →recent activity
Analyzing
Block #104,166,788
22 transactions · 16 stateful · 2026-09-12 11:22:57 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,166,788 · 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
6w07w18w29w311w416w517w018w621w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaeefeb3…889f
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
8 touches
6 conflicts
0x7054365a…650d
0x34b655…2a6f
7 touches
6 conflicts
0x7ce5b49a…237c
0x34b655…2a6f
6 touches
3 conflicts
0xc69d4d9e…8bcb
0x34b655…2a6f
4 touches
2 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
15 conflicts on slot 0xfaeefeb349…b8889f
Audit this contract →
← previous block·next block →recent activity