← previous blocknext block →recent activity
Analyzing
Block #99,183,827
10 transactions · 10 stateful · 2026-08-26 00:18:12 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,183,827 · 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
3w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf879fb7c…6785
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xac0b4a08…faae
0x34b655…2a6f
4 touches
1 conflict
0xd957b700…32be
0x34b655…2a6f
4 touches
1 conflict
0x391f578e…9a04
0x34b655…2a6f
3 touches
1 conflict
0x5883907e…2fd1
0x34b655…2a6f
3 touches
1 conflict
0x14ee7537…7ffb
0x34b655…2a6f
2 touches
0 conflicts
0x2bd8c8ca…8dc6
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xf879fb7c72…ca6785
Audit this contract →
← previous block·next block →recent activity