← previous blocknext block →recent activity
Analyzing
Block #100,153,151
18 transactions · 16 stateful · 2026-08-29 09:51:32 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,153,151 · 18 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
1w02w14w05w16w27w38w49w313w314w516w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e168c8b…6945
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xdbb9cf89…166c
0x34b655…2a6f
6 touches
3 conflicts
0x2c0fe9aa…dad9
0x34b655…2a6f
5 touches
3 conflicts
0x800856f0…3ee8
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
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
10 conflicts on slot 0x1e168c8bca…f56945
Audit this contract →
← previous block·next block →recent activity