← previous blocknext block →recent activity
Analyzing
Block #100,143,871
18 transactions · 15 stateful · 2026-08-29 09:04:49 UTC
Parallelism
72/100
Blocked
60%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,143,871 · 18 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
1w04w05w16w28w39w110w112w413w115w016w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fe611e7…87aa
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdc8d7edd…8a03
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
10 conflicts on slot 0x5fe611e7dd…9f87aa
Audit this contract →
← previous block·next block →recent activity