← previous blocknext block →recent activity
Analyzing
Block #100,603,484
39 transactions · 24 stateful · 2026-08-30 23:41:13 UTC
Parallelism
87/100
Blocked
46%
Avg conflicts / tx
0.51
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,603,484 · 39 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w08w09w111w217w019w120w226w131w234w135w136w237w338w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc9c17729…ac91
0x34b655…2a6f
6 touches
3 conflicts
0xb650b351…ae35
0xd32edf…ff58
5 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x41d3bfa5…523e
0x34b655…2a6f
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