← previous blocknext block →recent activity
Analyzing
Block #100,787,702
31 transactions · 26 stateful · 2026-08-31 15:08:03 UTC
Parallelism
74/100
Blocked
62%
Avg conflicts / tx
1.03
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,787,702 · 31 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w08w19w210w313w114w316w417w118w219w020w121w324w127w529w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x191e0467…70e5
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x79347b24…9fba
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xfad189f8…96e5
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x191e0467ba…1470e5
Audit this contract →
← previous block·next block →recent activity