← previous blocknext block →recent activity
Analyzing
Block #100,633,468
20 transactions · 20 stateful · 2026-08-31 02:12:03 UTC
Parallelism
65/100
Blocked
65%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,633,468 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w16w28w19w010w111w212w314w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x11b69a7e…334e
0xee8c0e…1242
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x45729b6f…f072
0x34b655…2a6f
6 touches
3 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
6 touches
3 conflicts
0xead15497…1dbe
0x34b655…2a6f
6 touches
3 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity