← previous blocknext block →recent activity
Analyzing
Block #106,542,479
25 transactions · 21 stateful · 2026-09-20 19:07:18 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,542,479 · 25 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
1w04w05w16w07w09w113w014w119w123w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
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
1 conflict on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity