← previous blocknext block →recent activity
Analyzing
Block #100,107,292
31 transactions · 28 stateful · 2026-08-29 06:00:30 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,107,292 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w08w19w010w112w014w115w016w017w118w119w222w325w128w029w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x667006b4…adc8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
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
3 conflicts on slot 0x631b41138f…31baa9
Audit this contract →
← previous block·next block →recent activity