← previous blocknext block →recent activity
Analyzing
Block #99,104,526
17 transactions · 14 stateful · 2026-08-25 17:39:09 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,104,526 · 17 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
1w02w010w113w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xaf86cd8e…83d2
0x34b655…2a6f
4 touches
1 conflict
0x38963aeb…c33f
0xa6afd3…d132
4 touches
1 conflict
0x0d11f6e9…c262
0xa6afd3…d132
3 touches
1 conflict
0x7ddd1d7c…7436
0xa6afd3…d132
3 touches
1 conflict
0x34724d7a…b996
0x34b655…2a6f
2 touches
0 conflicts
0x46abeefb…fc9c
0x34b655…2a6f
2 touches
0 conflicts
0x4de79789…7852
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity