← previous blocknext block →recent activity
Analyzing
Block #99,269,417
19 transactions · 17 stateful · 2026-08-26 07:28:55 UTC
Parallelism
84/100
Blocked
18%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,269,417 · 19 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
3w04w15w26w013w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91913ff0…97f8
0x34b655…2a6f
4 touches
1 conflict
0xe3684e08…c96a
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x059e0ac0…0267
0x34b655…2a6f
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x16665060…e752
0x34b655…2a6f
4 touches
1 conflict
0x37df7523…ccbb
0x754704…b603
2 touches
0 conflicts
0xb652da8f…1216
0x754704…b603
2 touches
0 conflicts
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 0x91913ff039…4497f8
Audit this contract →
← previous block·next block →recent activity