← previous blocknext block →recent activity
Analyzing
Block #105,930,031
28 transactions · 27 stateful · 2026-09-18 15:44:45 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,930,031 · 28 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
1w02w03w15w06w17w28w39w213w316w317w420w025w026w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17d87f0d…bfc5
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0x50b7cef1…a51a
0xee8c0e…1242
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe2dfa643…4853
0x34b655…2a6f
4 touches
1 conflict
0xefb236ca…f49b
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
3 conflicts on slot 0x17d87f0d74…03bfc5
Audit this contract →
← previous block·next block →recent activity