← previous blocknext block →recent activity
Analyzing
Block #104,166,776
18 transactions · 16 stateful · 2026-09-12 11:22:53 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
2.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,166,776 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w210w311w413w314w515w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d6da397…6c5c
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x28e2a536…7702
0x34b655…2a6f
14 touches
21 conflicts
0xea559e7b…41f4
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x4d6cf1f2…26f8
0x34b655…2a6f
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 0x5d6da39762…d36c5c
Audit this contract →
← previous block·next block →recent activity