← previous blocknext block →recent activity
Analyzing
Block #100,022,141
15 transactions · 12 stateful · 2026-08-28 22:51:50 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,022,141 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x68c740e2…58d6
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x02373c43…3cb3
0x34b655…2a6f
2 touches
0 conflicts
0x1e1541ce…9e06
0x34b655…2a6f
2 touches
0 conflicts
0x1f27d6ba…892e
0x34b655…2a6f
2 touches
0 conflicts
0x3a9149df…72e0
0x34b655…2a6f
2 touches
0 conflicts
0x3c78ca04…432c
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
1 conflict on slot 0x15698ac9db…df2a46
Audit this contract →
← previous block·next block →recent activity