← previous blocknext block →recent activity
Analyzing
Block #100,588,222
37 transactions · 35 stateful · 2026-08-30 22:24:26 UTC
Parallelism
86/100
Blocked
49%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,588,222 · 37 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
1w03w04w15w06w17w08w09w211w112w013w115w016w119w122w123w226w228w130w334w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x382434ca…96b5
0x34b655…2a6f
6 touches
3 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xdadd8b2d…f682
0xd32edf…ff58
5 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xe1ccb981…3f6b
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
6 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity