← previous blocknext block →recent activity
Analyzing
Block #100,983,818
19 transactions · 16 stateful · 2026-09-01 07:34:48 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,983,818 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w311w012w113w414w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2fd6de4…1729
0x34b655…2a6f
10 touches
10 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
8 touches
6 conflicts
0x9a100e05…c541
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0a3faaed…8179
0x34b655…2a6f
4 touches
1 conflict
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5434835d…650f
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
10 conflicts on slot 0xd2fd6de4a1…5c1729
Audit this contract →
← previous block·next block →recent activity