← previous blocknext block →recent activity
Analyzing
Block #99,700,028
24 transactions · 21 stateful · 2026-08-27 19:45:00 UTC
Parallelism
75/100
Blocked
57%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,700,028 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w18w29w010w113w214w315w416w320w221w323w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57e5abc1…286f
0x34b655…2a6f
8 touches
6 conflicts
0x736b9166…5ea5
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x65e6e603…cb44
0x34b655…2a6f
4 touches
1 conflict
0x65e6e603…cb45
0x34b655…2a6f
4 touches
1 conflict
0x6956d31b…6393
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x57e5abc14c…cb286f
Audit this contract →
← previous block·next block →recent activity