← previous blocknext block →recent activity
Analyzing
Block #100,786,337
32 transactions · 31 stateful · 2026-08-31 15:01:11 UTC
Parallelism
84/100
Blocked
52%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,786,337 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w39w310w011w113w014w015w116w217w318w219w422w223w427w131w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3042ff2…f600
0x34b655…2a6f
10 touches
10 conflicts
0xeeb1df16…4ad6
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x1045386d…cb88
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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
10 conflicts on slot 0xc3042ff2e7…a9f600
Audit this contract →
← previous block·next block →recent activity