← previous blocknext block →recent activity
Analyzing
Block #99,473,434
13 transactions · 13 stateful · 2026-08-27 00:35:57 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,473,434 · 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
1w03w14w211w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17c3727d…cb0e
0x34b655…2a6f
6 touches
3 conflicts
0xdcebb2b8…5f18
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9c6f2f5b…185e
0x34b655…2a6f
4 touches
1 conflict
0xb3c45140…3aef
0x34b655…2a6f
4 touches
1 conflict
0xc2db6e7a…d074
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 0x17c3727da3…18cb0e
Audit this contract →
← previous block·next block →recent activity