← previous blocknext block →recent activity
Analyzing
Block #99,275,454
24 transactions · 21 stateful · 2026-08-26 07:59:16 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,275,454 · 24 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
1w02w14w05w17w114w215w016w120w021w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb7da640…b03d
0x34b655…2a6f
4 touches
1 conflict
0xe3abe489…ebfc
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ec0b
0x77d53b…8080
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
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
1 conflict on slot 0xeb7da6405f…42b03d
Audit this contract →
← previous block·next block →recent activity