← previous blocknext block →recent activity
Analyzing
Block #104,915,862
20 transactions · 20 stateful · 2026-09-15 02:38:03 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,915,862 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w07w18w110w213w114w215w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd7f5b55…4994
0x34b655…2a6f
6 touches
3 conflicts
0xbbdfd584…ab2f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x6003ae26…25c5
0x34b655…2a6f
4 touches
1 conflict
0x961de36a…e135
0x34b655…2a6f
4 touches
1 conflict
0x904bb1d5…0100
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
3 conflicts on slot 0xfd7f5b557f…f74994
Audit this contract →
← previous block·next block →recent activity