← previous blocknext block →recent activity
Analyzing
Block #100,731,540
31 transactions · 29 stateful · 2026-08-31 10:25:23 UTC
Parallelism
52/100
Blocked
66%
Avg conflicts / tx
2.1
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #100,731,540 · 31 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w07w18w29w310w411w012w113w414w515w616w318w724w825w926w1027w1128w1229w1330w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x326a02b5…8dad
0x34b655…2a6f
14 touches
21 conflicts
0x62910921…3016
0x34b655…2a6f
10 touches
10 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
10 touches
10 conflicts
0xf620f2c4…773e
0x34b655…2a6f
8 touches
6 conflicts
0xfac61869…a55c
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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: Perpl
28 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity