← previous blocknext block →recent activity
Analyzing
Block #100,747,796
23 transactions · 23 stateful · 2026-08-31 11:47:09 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,747,796 · 23 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
3w04w17w08w19w010w111w212w313w314w415w516w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34fe25fc…0293
0x34b655…2a6f
12 touches
15 conflicts
0x382434ca…96b5
0x34b655…2a6f
10 touches
10 conflicts
0x0a2131b3…455e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x651d58a1…9f16
0x34b655…2a6f
6 touches
3 conflicts
0xef048f92…572b
0x34b655…2a6f
6 touches
3 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
6 touches
3 conflicts
0x1408a100…f721
0x34b655…2a6f
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
15 conflicts on slot 0x34fe25fcc8…a30293
Audit this contract →
← previous block·next block →recent activity