← previous blocknext block →recent activity
Analyzing
Block #100,093,767
23 transactions · 20 stateful · 2026-08-29 04:52:24 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,093,767 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w07w18w211w012w213w314w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cc500b1…55cd
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe9e0e11e…6373
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0x631b4113…baa9
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
3 conflicts on slot 0x6cc500b1da…a855cd
Audit this contract →
← previous block·next block →recent activity