← previous blocknext block →recent activity
Analyzing
Block #99,496,496
13 transactions · 13 stateful · 2026-08-27 02:32:06 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,496,496 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w16w29w011w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcebb2b8…5f18
0x34b655…2a6f
8 touches
6 conflicts
0xc95f91db…a901
0x34b655…2a6f
6 touches
3 conflicts
0x9c6f2f5b…185e
0x34b655…2a6f
4 touches
1 conflict
0xb3c45140…3aef
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
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
6 conflicts on slot 0xdcebb2b809…7d5f18
Audit this contract →
← previous block·next block →recent activity