← previous blocknext block →recent activity
Analyzing
Block #99,607,587
10 transactions · 10 stateful · 2026-08-27 11:56:25 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,607,587 · 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
1w02w03w14w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x206c55db…94ea
0x34b655…2a6f
4 touches
1 conflict
0x47e835ac…5af0
0x34b655…2a6f
4 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x8cd2adea…71aa
0x34b655…2a6f
4 touches
1 conflict
0xbe6835a1…a184
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
1 conflict on slot 0x206c55db29…6b94ea
Audit this contract →
← previous block·next block →recent activity