← previous blocknext block →recent activity
Analyzing
Block #106,155,880
25 transactions · 24 stateful · 2026-09-19 10:41:33 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,155,880 · 25 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
2w03w14w25w18w09w110w212w017w019w022w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x4b024b98…8f37
0x34b655…2a6f
4 touches
1 conflict
0x60ffc0ea…6a07
0x34b655…2a6f
4 touches
1 conflict
0x67c1f465…38b3
0x34b655…2a6f
4 touches
1 conflict
0x83afd9e0…dc1d
0x34b655…2a6f
4 touches
1 conflict
0x8a7b72db…3f9c
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity