← previous blocknext block →recent activity
Analyzing
Block #106,453,547
20 transactions · 17 stateful · 2026-09-20 11:39:44 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,453,547 · 20 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
2w03w14w19w210w312w413w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad1d9367…3f9d
0x34b655…2a6f
12 touches
15 conflicts
0xfe890a5b…ac60
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
8 touches
6 conflicts
0xa5811d93…8c73
0x34b655…2a6f
8 touches
6 conflicts
0x038b9243…553d
0x34b655…2a6f
6 touches
3 conflicts
0xe8058ec4…ebac
0x34b655…2a6f
4 touches
1 conflict
0xf5b2ef24…06f5
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 0xad1d936705…663f9d
Audit this contract →
← previous block·next block →recent activity