← previous blocknext block →recent activity
Analyzing
Block #100,022,269
16 transactions · 14 stateful · 2026-08-28 22:52:29 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,022,269 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w09w110w211w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65b5c7f0…57ef
0x34b655…2a6f
10 touches
10 conflicts
0x6d5c5d72…914b
0x34b655…2a6f
8 touches
6 conflicts
0x7c1fdb07…5e8d
0x34b655…2a6f
6 touches
3 conflicts
0x17df350f…ad97
0x34b655…2a6f
6 touches
3 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
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
10 conflicts on slot 0x65b5c7f077…9f57ef
Audit this contract →
← previous block·next block →recent activity