← previous blocknext block →recent activity
Analyzing
Block #100,131,045
17 transactions · 17 stateful · 2026-08-29 08:00:06 UTC
Parallelism
59/100
Blocked
59%
Avg conflicts / tx
1.41
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,131,045 · 17 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
2w04w05w17w18w29w310w411w512w513w114w216w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ce1b956…48c9
0x34b655…2a6f
12 touches
15 conflicts
0x2b43dd7d…7f99
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc13e1d5c…62c6
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x038b9243…553d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
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 0x1ce1b956c5…6b48c9
Audit this contract →
← previous block·next block →recent activity