← previous blocknext block →recent activity
Analyzing
Block #104,983,722
32 transactions · 32 stateful · 2026-09-15 08:19:31 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,983,722 · 32 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
2w03w04w05w18w19w210w311w412w513w614w015w117w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7ecbbe7…f713
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xcd93b2d2…30e6
0x34b655…2a6f
12 touches
15 conflicts
0xbc0b43b0…35d6
0x34b655…2a6f
12 touches
15 conflicts
0x06343fc1…ba88
0x34b655…2a6f
6 touches
3 conflicts
0xff7657e6…a4b7
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x9c6a9da2…c628
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 0xa7ecbbe767…04f713
Audit this contract →
← previous block·next block →recent activity