← previous blocknext block →recent activity
Analyzing
Block #99,880,281
30 transactions · 25 stateful · 2026-08-28 10:57:08 UTC
Parallelism
90/100
Blocked
44%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,880,281 · 30 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w09w010w011w113w114w215w117w121w123w125w228w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x733c7779…a647
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xdb40334f…e0bc
0xa6afd3…d132
6 touches
3 conflicts
0x931975c2…b7b3
0x34b655…2a6f
6 touches
3 conflicts
0x40970e69…da50
0x2b46c0…1669
4 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
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 0x733c7779fd…f4a647
Audit this contract →
← previous block·next block →recent activity