← previous blocknext block →recent activity
Analyzing
Block #100,703,912
19 transactions · 19 stateful · 2026-08-31 08:06:23 UTC
Parallelism
58/100
Blocked
47%
Avg conflicts / tx
0.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,703,912 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w310w312w414w515w616w718w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e168c8b…6945
0x34b655…2a6f
8 touches
6 conflicts
0x10370534…235b
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xe5060fe3…ebe3
0x1b6862…e19c
4 touches
1 conflict
0x0e32b468…80a7
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 0x1e168c8bca…f56945
Audit this contract →
← previous block·next block →recent activity