← previous blocknext block →recent activity
Analyzing
Block #100,786,184
25 transactions · 23 stateful · 2026-08-31 15:00:24 UTC
Parallelism
60/100
Blocked
57%
Avg conflicts / tx
1.88
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,786,184 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w19w210w311w412w513w614w715w818w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c68d10b…8386
0x34b655…2a6f
18 touches
36 conflicts
0x02dab2c8…5cb1
0x34b655…2a6f
12 touches
15 conflicts
0x7504da64…542f
0x34b655…2a6f
12 touches
15 conflicts
0xbc048bb8…5df6
0x34b655…2a6f
10 touches
10 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
10 touches
10 conflicts
0x28eed2ad…c4b2
0x34b655…2a6f
10 touches
10 conflicts
0xba1edffb…323e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
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
36 conflicts on slot 0x7c68d10b83…628386
Audit this contract →
← previous block·next block →recent activity