← previous blocknext block →recent activity
Analyzing
Block #106,958,624
28 transactions · 25 stateful · 2026-09-22 06:02:49 UTC
Parallelism
89/100
Blocked
40%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,958,624 · 28 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
1w02w13w04w15w06w18w010w112w013w116w017w118w019w120w021w124w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85c2666e…5acf
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x16586475…53db
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0x4786839b…c29a
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: 0x99c7a72e…c78bf0
1 conflict on slot 0x85c2666e22…c55acf
Audit this contract →
← previous block·next block →recent activity