← previous blocknext block →recent activity
Analyzing
Block #100,619,293
15 transactions · 15 stateful · 2026-08-31 01:00:45 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,619,293 · 15 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
3w04w05w16w07w08w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xfd7f5b55…4994
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xb3037bed…6b7c
0x34b655…2a6f
4 touches
1 conflict
0x4f34154d…8509
0x34b655…2a6f
2 touches
0 conflicts
0x5d130ef2…b51b
0x34b655…2a6f
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity