← previous blocknext block →recent activity
Analyzing
Block #105,461,641
18 transactions · 17 stateful · 2026-09-17 00:25:00 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,461,641 · 18 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
3w04w18w29w010w112w315w016w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x178a61ad…4958
0x34b655…2a6f
8 touches
6 conflicts
0xbbd1a344…ec7c
0x34b655…2a6f
8 touches
6 conflicts
0xf496f80c…d5c8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xee8237bd…46ad
0x34b655…2a6f
6 touches
3 conflicts
0xd1111945…ebd2
0x34b655…2a6f
4 touches
1 conflict
0xf3a6d515…09e2
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7c
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
6 conflicts on slot 0x178a61ad8a…8c4958
Audit this contract →
← previous block·next block →recent activity