← previous blocknext block →recent activity
Analyzing
Block #104,197,281
11 transactions · 11 stateful · 2026-09-12 13:57:39 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,197,281 · 11 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
4w05w07w18w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x64d353bf…54eb
0x34b655…2a6f
4 touches
1 conflict
0x64d353bf…54ec
0x34b655…2a6f
4 touches
1 conflict
0xb00be527…3e3a
0x34b655…2a6f
4 touches
1 conflict
0xd6255b52…69e7
0x34b655…2a6f
4 touches
1 conflict
0x02f03914…a304
0x34b655…2a6f
4 touches
1 conflict
0x00b3a403…9984
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity