← previous blocknext block →recent activity
Analyzing
Block #106,301,636
16 transactions · 15 stateful · 2026-09-19 22:55:09 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,301,636 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x14b3d8cc…c14d
0xa6afd3…d132
4 touches
1 conflict
0x6435d629…c725
0xa6afd3…d132
4 touches
1 conflict
0x214f87c0…9db8
0x34b655…2a6f
4 touches
1 conflict
0x7fec4dea…6005
0x34b655…2a6f
2 touches
0 conflicts
0xa57576bb…e01f
0x34b655…2a6f
2 touches
0 conflicts
0xab1e47c4…84b1
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity