← previous blocknext block →recent activity
Analyzing
Block #100,923,280
24 transactions · 21 stateful · 2026-09-01 02:30:17 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,923,280 · 24 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
1w02w15w06w17w08w113w115w216w318w319w221w022w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81957e96…a0cb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6caf33e2…c261
0x34b655…2a6f
6 touches
3 conflicts
0x23529e13…6f25
0x34b655…2a6f
6 touches
3 conflicts
0x496a9b1d…c655
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641e
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 0x81957e96e7…33a0cb
Audit this contract →
← previous block·next block →recent activity