← previous blocknext block →recent activity
Analyzing
Block #100,094,297
26 transactions · 22 stateful · 2026-08-29 04:55:04 UTC
Parallelism
69/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,094,297 · 26 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
1w02w16w17w28w210w311w413w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5b70be7…07b7
0x34b655…2a6f
10 touches
10 conflicts
0x61571888…b392
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb5
0x1b6862…e19c
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: Perpl
10 conflicts on slot 0xe5b70be72a…6007b7
Audit this contract →
← previous block·next block →recent activity