← previous blocknext block →recent activity
Analyzing
Block #99,170,506
15 transactions · 15 stateful · 2026-08-25 23:11:11 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,170,506 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w010w111w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fb8364c…c10d
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xabfdfd0e…20bf
0x34b655…2a6f
6 touches
3 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0x8714eb4d…e184
0x34b655…2a6f
4 touches
1 conflict
0xa7f7a563…4504
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 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
3 conflicts on slot 0x1fb8364c98…f7c10d
Audit this contract →
← previous block·next block →recent activity