← previous blocknext block →recent activity
Analyzing
Block #100,094,822
19 transactions · 17 stateful · 2026-08-29 04:57:43 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,094,822 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w08w09w010w111w112w213w315w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe1681c4c…5858
0x34b655…2a6f
8 touches
6 conflicts
0xef048f92…572b
0x34b655…2a6f
8 touches
6 conflicts
0x981b3d0c…457e
0x34b655…2a6f
8 touches
6 conflicts
0xd7e4217d…7c6b
0x34b655…2a6f
8 touches
6 conflicts
0x9ff94a68…7ae8
0x34b655…2a6f
7 touches
6 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
6 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity