← previous blocknext block →recent activity
Analyzing
Block #106,423,733
16 transactions · 15 stateful · 2026-09-20 09:09:37 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,423,733 · 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
1w02w03w14w26w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe9d1d23…3de2
0x34b655…2a6f
6 touches
3 conflicts
0x2f27faea…dca1
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0x8590b692…b267
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0df715f3…1601
0x34b655…2a6f
4 touches
1 conflict
0x2f74f175…9287
0x34ae4d…3fc5
2 touches
0 conflicts
0x3ba7edbb…80e6
0x34ae4d…3fc5
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
3 conflicts on slot 0xbe9d1d2362…0d3de2
Audit this contract →
← previous block·next block →recent activity