← previous blocknext block →recent activity
Analyzing
Block #105,856,489
19 transactions · 18 stateful · 2026-09-18 09:33:44 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,856,489 · 19 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
4w06w19w110w211w312w413w514w618w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7fa076c…7d92
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x297de2d5…7396
0x34b655…2a6f
14 touches
21 conflicts
0x59209c69…415b
0x34b655…2a6f
10 touches
10 conflicts
0xfefb0189…f726
0x34b655…2a6f
8 touches
6 conflicts
0x43e3decb…be40
0x34b655…2a6f
6 touches
3 conflicts
0x773a17af…fa16
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0xd7fa076c04…697d92
Audit this contract →
← previous block·next block →recent activity