← previous blocknext block →recent activity
Analyzing
Block #107,651,432
23 transactions · 21 stateful · 2026-09-24 16:11:06 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,651,432 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w09w110w211w312w313w414w515w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d477ec1…5020
0x34b655…2a6f
10 touches
10 conflicts
0x25957369…c648
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x94e7f277…471b
0x34b655…2a6f
6 touches
3 conflicts
0x43e3decb…be40
0x34b655…2a6f
6 touches
3 conflicts
0xedecf855…ca4a
0x34b655…2a6f
6 touches
3 conflicts
0xf78a2e03…f457
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x2d477ec1ee…b85020
Audit this contract →
← previous block·next block →recent activity