← previous blocknext block →recent activity
Analyzing
Block #105,925,476
39 transactions · 33 stateful · 2026-09-18 15:21:49 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.51
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,925,476 · 39 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
2w03w14w26w316w017w118w219w322w424w427w031w135w237w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x08f9abf1…10bf
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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