← previous blocknext block →recent activity
Analyzing
Block #105,582,992
23 transactions · 22 stateful · 2026-09-17 10:35:42 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,582,992 · 23 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
2w03w04w05w16w110w011w112w213w314w415w516w619w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x581f7011…eb5b
0x34b655…2a6f
14 touches
21 conflicts
0xee8237bd…46ad
0x34b655…2a6f
10 touches
10 conflicts
0xca608d0c…f23b
0x34b655…2a6f
8 touches
6 conflicts
0x818e1296…f4d7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
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 0x581f701126…13eb5b
Audit this contract →
← previous block·next block →recent activity