← previous blocknext block →recent activity
Analyzing
Block #99,958,530
16 transactions · 14 stateful · 2026-08-28 17:31:30 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,958,530 · 16 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
1w02w13w05w07w18w010w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801dc9d2…26c1
0x99c7a7…8bf0
4 touches
1 conflict
0xc6620147…085b
0x754704…b603
4 touches
1 conflict
0xe066f7b8…af57
0x754704…b603
4 touches
1 conflict
0x6864f935…f4fc
0x99c7a7…8bf0
4 touches
1 conflict
0xf8598d75…4a33
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x021cd478…a6d4
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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: 0x99c7a72e…c78bf0
1 conflict on slot 0x801dc9d226…4f26c1
Audit this contract →
← previous block·next block →recent activity