← previous blocknext block →recent activity
Analyzing
Block #100,604,447
120 transactions · 60 stateful · 2026-08-30 23:46:04 UTC
Parallelism
84/100
Blocked
82%
Avg conflicts / tx
2.45
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #100,604,447 · 120 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w467w369w571w775w977w1078w1179w1283w1290w1392w14107w15116w5117w6118w7119w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
30 touches
105 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0x00000000…00c9
0x34b655…2a6f
20 touches
45 conflicts
0x20be6928…b9b0
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0002
0xf5b5f7…6d70
14 touches
21 conflicts
0x7d4f80a4…bb19
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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
105 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity