← previous blocknext block →recent activity
Analyzing
Block #100,627,092
25 transactions · 23 stateful · 2026-08-31 01:39:58 UTC
Parallelism
72/100
Blocked
57%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,627,092 · 25 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
1w03w04w16w17w18w29w310w212w313w014w416w418w223w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba47bf84…72f3
0x34b655…2a6f
10 touches
10 conflicts
0xb7ce83b1…2c96
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xb77dc863…dd3d
0x34b655…2a6f
6 touches
3 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
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 0xba47bf84f8…2c72f3
Audit this contract →
← previous block·next block →recent activity