← previous blocknext block →recent activity
Analyzing
Block #100,122,141
16 transactions · 15 stateful · 2026-08-29 07:15:17 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,122,141 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w28w39w410w011w513w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8a8db2…8a6d
0x34b655…2a6f
10 touches
10 conflicts
0x1d48c0e2…b62e
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x91220b8f…7a06
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 0x5c8a8db2ad…f58a6d
Audit this contract →
← previous block·next block →recent activity