← previous blocknext block →recent activity
Analyzing
Block #100,024,240
15 transactions · 14 stateful · 2026-08-28 23:02:24 UTC
Parallelism
47/100
Blocked
50%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,024,240 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf494f6c9…714f
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xca2b4ab7…5236
0x34b655…2a6f
8 touches
6 conflicts
0xcd232ca9…031a
0x34b655…2a6f
8 touches
6 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
8 touches
6 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
8 touches
6 conflicts
0xe283e878…7262
0x34b655…2a6f
8 touches
6 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xf494f6c99a…52714f
Audit this contract →
← previous block·next block →recent activity