← previous blocknext block →recent activity
Analyzing
Block #99,209,017
14 transactions · 12 stateful · 2026-08-26 02:24:56 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,209,017 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w09w110w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcdd58ff…0711
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2095236c…26d6
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x997ccc40…4dfd
0x3bd359…433a
2 touches
0 conflicts
0x0b552eae…fbd9
0x754704…b603
2 touches
0 conflicts
0x13477596…b14c
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 0xbcdd58ff98…970711
Audit this contract →
← previous block·next block →recent activity