← previous blocknext block →recent activity
Analyzing
Block #106,953,464
21 transactions · 19 stateful · 2026-09-22 05:36:51 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,953,464 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w17w18w29w310w012w115w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebb97840…6a07
0x34b655…2a6f
12 touches
15 conflicts
0xab41643c…f9bf
0x34b655…2a6f
10 touches
10 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 conflicts
0x8d5fc820…1750
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x5ce28434…11ee
0x34b655…2a6f
6 touches
3 conflicts
0x5e2ea201…12de
0x34b655…2a6f
4 touches
1 conflict
0x6c26d635…1bbf
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
15 conflicts on slot 0xebb9784078…df6a07
Audit this contract →
← previous block·next block →recent activity