← previous blocknext block →recent activity
Analyzing
Block #99,987,005
20 transactions · 20 stateful · 2026-08-28 19:54:58 UTC
Parallelism
90/100
Blocked
15%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,987,005 · 20 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
5w06w111w014w016w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70a7b5d6…fe0e
0x34b655…2a6f
4 touches
1 conflict
0x191e0467…70e5
0x34b655…2a6f
4 touches
1 conflict
0x9ad82ccb…b08b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x2dc33e18…3b26
0x34b655…2a6f
3 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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 0x70a7b5d69a…6cfe0e
Audit this contract →
← previous block·next block →recent activity