← previous blocknext block →recent activity
Analyzing
Block #100,750,846
44 transactions · 28 stateful · 2026-08-31 12:02:29 UTC
Parallelism
84/100
Blocked
36%
Avg conflicts / tx
0.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,750,846 · 44 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w110w011w112w213w022w232w034w135w140w341w442w543w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x71a923ba…41eb
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x5086c64a…28ba
0x34b655…2a6f
6 touches
3 conflicts
0x89ac61bf…9443
0x34b655…2a6f
6 touches
3 conflicts
0x5fba4b48…16c0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity