← previous blocknext block →recent activity
Analyzing
Block #100,460,349
14 transactions · 13 stateful · 2026-08-30 11:41:09 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,460,349 · 14 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
1w04w16w07w19w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xff9e45bf…99a0
0x34b655…2a6f
6 touches
3 conflicts
0x56fd4073…d334
0x34b655…2a6f
4 touches
1 conflict
0x5784baac…ac7e
0x34b655…2a6f
4 touches
1 conflict
0x6636a104…d595
0x34b655…2a6f
4 touches
1 conflict
0x884cfd8a…51c6
0x34b655…2a6f
4 touches
1 conflict
0x884fdb86…ac60
0x34b655…2a6f
4 touches
1 conflict
0x9c83a7b1…e305
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity