← previous blocknext block →recent activity
Analyzing
Block #100,587,002
28 transactions · 21 stateful · 2026-08-30 22:18:18 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,587,002 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w09w110w212w016w318w120w121w223w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0f5d668…99ac
0x34b655…2a6f
8 touches
6 conflicts
0xbd590df7…9891
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
8 touches
6 conflicts
0x52640507…df00
0x34b655…2a6f
7 touches
6 conflicts
0xb8120f7a…ae3c
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xb0f5d66855…1a99ac
Audit this contract →
← previous block·next block →recent activity