← previous blocknext block →recent activity
Analyzing
Block #105,930,657
24 transactions · 22 stateful · 2026-09-18 15:47:54 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,930,657 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w011w012w113w214w318w120w021w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x5d0915af…762d
0x34b655…2a6f
6 touches
3 conflicts
0x728a2ddc…ce25
0x34b655…2a6f
4 touches
1 conflict
0x8b3e062c…489a
0x34b655…2a6f
4 touches
1 conflict
0x8eeaf224…9eec
0x34b655…2a6f
4 touches
1 conflict
0xa5904747…afe9
0x34b655…2a6f
4 touches
1 conflict
0xa6cb8d47…4f25
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity