← previous blocknext block →recent activity
Analyzing
Block #106,329,628
32 transactions · 28 stateful · 2026-09-20 01:16:01 UTC
Parallelism
78/100
Blocked
64%
Avg conflicts / tx
1.28
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,329,628 · 32 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
1w04w05w06w17w28w39w410w112w116w318w219w320w421w526w129w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x735a86cd…b64d
0x34b655…2a6f
12 touches
15 conflicts
0x1715a62a…7b93
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x04894ced…7ce8
0xd32edf…ff58
5 touches
3 conflicts
0x67ac165d…3f65
0x065c9d…c394
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity