← previous blocknext block →recent activity
Analyzing
Block #106,952,592
37 transactions · 30 stateful · 2026-09-22 05:32:27 UTC
Parallelism
89/100
Blocked
37%
Avg conflicts / tx
0.49
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,952,592 · 37 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
1w03w15w06w17w08w19w010w116w218w219w022w323w225w226w329w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xe4c5e368…89b9
0x065c9d…c394
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x39f2deb5…0c60
0x34b655…2a6f
4 touches
1 conflict
0x3eb48ea2…eef2
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0x49b9fdd5ff…6f9c16
Audit this contract →
← previous block·next block →recent activity