← previous blocknext block →recent activity
Analyzing
Block #106,945,614
16 transactions · 16 stateful · 2026-09-22 04:57:20 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,945,614 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w16w28w09w010w111w013w214w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37eb66f0…f797
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x704a8131…bbe8
0x34b655…2a6f
4 touches
1 conflict
0x91cd366d…5cea
0x34b655…2a6f
4 touches
1 conflict
0x94dabb65…43a3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x37eb66f086…06f797
Audit this contract →
← previous block·next block →recent activity