← previous blocknext block →recent activity
Analyzing
Block #100,790,120
23 transactions · 21 stateful · 2026-08-31 15:20:14 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,790,120 · 23 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
1w04w15w09w011w012w113w014w116w017w018w220w222w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x329f9fde…fe9c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x2827ae77…4368
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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: Perpl
3 conflicts on slot 0x329f9fde20…89fe9c
Audit this contract →
← previous block·next block →recent activity