← previous blocknext block →recent activity
Analyzing
Block #100,877,337
16 transactions · 15 stateful · 2026-08-31 22:39:12 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,877,337 · 16 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
1w03w16w07w18w210w111w312w215w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb450d6cf…be0b
0x34b655…2a6f
8 touches
6 conflicts
0xf38a3927…ad62
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x75e73565…45f8
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0xb450d6cfe1…bfbe0b
Audit this contract →
← previous block·next block →recent activity