← previous blocknext block →recent activity
Analyzing
Block #100,858,539
18 transactions · 16 stateful · 2026-08-31 21:04:39 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,858,539 · 18 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
1w02w13w25w38w010w011w112w213w314w415w116w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba4267da…2d50
0x40c49f…2af0
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x3e1e8e54…9c83
0x2a68ba…90c5
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x872e51c8…ae29
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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: 0x40c49f17…d22af0
10 conflicts on slot 0xba4267da10…df2d50
Audit this contract →
← previous block·next block →recent activity