← previous blocknext block →recent activity
Analyzing
Block #99,503,596
19 transactions · 19 stateful · 2026-08-27 03:07:50 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,503,596 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w06w17w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c1b956d…14d3
0x34b655…2a6f
6 touches
3 conflicts
0xeffd747c…6a01
0x851145…3f07
4 touches
1 conflict
0x309be735…8510
0x34b655…2a6f
4 touches
1 conflict
0x3d8d3799…f709
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc4655c58…c135
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x5c1b956d4c…d014d3
Audit this contract →
← previous block·next block →recent activity