← previous blocknext block →recent activity
Analyzing
Block #99,253,743
10 transactions · 9 stateful · 2026-08-26 06:09:58 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,253,743 · 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
1w02w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0xa7199234…a277
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x2274142b…f885
0x851145…3f07
4 touches
1 conflict
0x8b98c194…d69e
0x851145…3f07
4 touches
1 conflict
0x8467be6d…a718
0x851145…3f07
3 touches
1 conflict
0x91ab5688…470d
0x851145…3f07
3 touches
1 conflict
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 0x5ad5e6deb1…38e7ad
Audit this contract →
← previous block·next block →recent activity