← previous blocknext block →recent activity
Analyzing
Block #100,132,423
97 transactions · 90 stateful · 2026-08-29 08:07:02 UTC
Parallelism
98/100
Blocked
1%
Avg conflicts / tx
0.01
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,132,423 · 97 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
12w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0476d77b…a514
0x34b655…2a6f
2 touches
0 conflicts
0x37bdecf8…b358
0x34b655…2a6f
2 touches
0 conflicts
0x3f85ce09…e4cc
0x34b655…2a6f
2 touches
0 conflicts
0x5f453c44…fa94
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity