← previous blocknext block →recent activity
Analyzing
Block #99,317,468
17 transactions · 17 stateful · 2026-08-26 11:30:37 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,317,468 · 17 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
2w03w14w05w16w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf996a00d…e31c
0x99c7a7…8bf0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x023b4f90…6425
0x34b655…2a6f
4 touches
1 conflict
0x3a40dd6e…002f
0x754704…b603
4 touches
1 conflict
0x5edee0b9…f802
0x754704…b603
4 touches
1 conflict
0xa28f5ba9…05c9
0x754704…b603
4 touches
1 conflict
0x88a7e561…8827
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
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: 0x99c7a72e…c78bf0
1 conflict on slot 0xf996a00d97…83e31c
Audit this contract →
← previous block·next block →recent activity