← previous blocknext block →recent activity
Analyzing
Block #99,617,295
21 transactions · 15 stateful · 2026-08-27 12:46:23 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,617,295 · 21 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
1w06w09w116w217w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39ccd26a…4654
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd1203697…1ae0
0x40c49f…2af0
4 touches
1 conflict
0x6fce7a05…d778
0x34b655…2a6f
4 touches
1 conflict
0x733edb92…4e80
0x34b655…2a6f
4 touches
1 conflict
0xa5aa813a…bb9b
0x34b655…2a6f
4 touches
1 conflict
0xb856d1a1…1f18
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
6 conflicts on slot 0x39ccd26aaf…a04654
Audit this contract →
← previous block·next block →recent activity