← previous blocknext block →recent activity
Analyzing
Block #100,134,653
10 transactions · 10 stateful · 2026-08-29 08:18:16 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,134,653 · 10 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0xd4a49e7f…cec6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x64a785e4…0110
0x34b655…2a6f
2 touches
0 conflicts
0xd58e5c6b…7188
0x34b655…2a6f
2 touches
0 conflicts
0xdb3937e8…23cb
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 0x08e8f2c94d…1ca11a
Audit this contract →
← previous block·next block →recent activity