← previous blocknext block →recent activity
Analyzing
Block #100,460,308
16 transactions · 13 stateful · 2026-08-30 11:40:57 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,460,308 · 16 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
6w07w19w110w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2a6ee72…96b3
0x34b655…2a6f
6 touches
3 conflicts
0x3e2681f7…2a4f
0x34b655…2a6f
6 touches
3 conflicts
0x9dccd2a9…2790
0x34b655…2a6f
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0x9a8482cc…8bee
0x34b655…2a6f
4 touches
1 conflict
0x9c83a7b1…e305
0x34b655…2a6f
4 touches
1 conflict
0xd5c56995…6d21
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 0xe2a6ee729a…1c96b3
Audit this contract →
← previous block·next block →recent activity