← previous blocknext block →recent activity
Analyzing
Block #99,208,445
16 transactions · 15 stateful · 2026-08-26 02:22:03 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,208,445 · 16 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
4w08w19w010w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x498ed94c…967d
0x34b655…2a6f
4 touches
1 conflict
0xabdf81c9…b3b0
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xefeb7937…c283
0x34b655…2a6f
4 touches
1 conflict
0xf85bdc12…5dff
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x22265c56…1063
0x34b655…2a6f
4 touches
1 conflict
0x8322e16e…127c
0x065c9d…c394
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 0x498ed94ccc…f0967d
Audit this contract →
← previous block·next block →recent activity