← previous blocknext block →recent activity
Analyzing
Block #100,021,998
21 transactions · 19 stateful · 2026-08-28 22:51:07 UTC
Parallelism
86/100
Blocked
26%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,021,998 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w010w112w013w115w219w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e3014f0…b4e1
0x34b655…2a6f
6 touches
3 conflicts
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x00f6a8a7…0e6e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x54919cee…dd00
0x34b655…2a6f
4 touches
1 conflict
0x6a673ab4…355a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x5e3014f0c7…b1b4e1
Audit this contract →
← previous block·next block →recent activity