← previous blocknext block →recent activity
Analyzing
Block #106,420,897
9 transactions · 9 stateful · 2026-09-20 08:55:20 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,420,897 · 9 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
1w02w03w14w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xb5d1cad9…40b0
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x9708602e…de14
0x34b655…2a6f
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
2 touches
0 conflicts
0xd6209a50…9955
0x065c9d…c394
2 touches
0 conflicts
0xd9460dd9…a664
0x065c9d…c394
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 0x3fa1fac42c…ba826c
Audit this contract →
← previous block·next block →recent activity