← previous blocknext block →recent activity
Analyzing
Block #105,619,600
24 transactions · 22 stateful · 2026-09-17 13:40:00 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,619,600 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w17w08w19w210w311w112w216w218w321w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaefff698…0433
0x065c9d…c394
3 touches
1 conflict
0x00000000…0000
0x81e8ed…9c15
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: 0xf5b5f7f8…a36d70
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity