← previous blocknext block →recent activity
Analyzing
Block #100,924,001
20 transactions · 16 stateful · 2026-09-01 02:33:55 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
1.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,924,001 · 20 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
1w02w13w25w06w07w110w213w314w415w516w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x3aedb1fd…db38
0x34b655…2a6f
8 touches
6 conflicts
0x25180879…8191
0x34b655…2a6f
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x193fe67a…7d9a
0x065c9d…c394
6 touches
3 conflicts
0xf3e51cd3…a9b4
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity