← previous blocknext block →recent activity
Analyzing
Block #100,432,581
25 transactions · 24 stateful · 2026-08-30 09:21:22 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,432,581 · 25 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
2w03w06w09w010w112w214w315w416w519w120w621w122w724w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e841543…7683
0x34b655…2a6f
12 touches
15 conflicts
0x297de2d5…7396
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8beac61f…f999
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa6464996…3af9
0x34b655…2a6f
6 touches
3 conflicts
0x262ffe69…b552
0x34b655…2a6f
4 touches
1 conflict
0x2c2db8e9…fdc7
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
15 conflicts on slot 0x7e841543c9…837683
Audit this contract →
← previous block·next block →recent activity