← previous blocknext block →recent activity
Analyzing
Block #99,619,232
17 transactions · 16 stateful · 2026-08-27 12:56:19 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,619,232 · 17 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
1w02w13w27w08w112w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe6835a1…a184
0x34b655…2a6f
6 touches
3 conflicts
0xe10e20f8…ca1b
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x16d77246…bac5
0x34b655…2a6f
4 touches
1 conflict
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0x5c12ac0e…fb32
0x34b655…2a6f
4 touches
1 conflict
0xb3af6b7b…bba9
0x34b655…2a6f
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 0xbe6835a18c…f1a184
Audit this contract →
← previous block·next block →recent activity