← previous blocknext block →recent activity
Analyzing
Block #100,614,200
34 transactions · 25 stateful · 2026-08-31 00:35:08 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,614,200 · 34 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
1w02w14w07w29w010w011w120w021w222w124w226w128w130w331w432w533w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15698ac9…2a46
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0x9144e3a9…3d6e
0x34b655…2a6f
6 touches
3 conflicts
0x3c9eb1c3…9acf
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
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
10 conflicts on slot 0x15698ac9db…df2a46
Audit this contract →
← previous block·next block →recent activity