← previous blocknext block →recent activity
Analyzing
Block #100,739,147
19 transactions · 17 stateful · 2026-08-31 11:03:38 UTC
Parallelism
74/100
Blocked
59%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,739,147 · 19 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
1w02w14w07w18w29w010w111w212w313w114w417w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56fe17b8…39b1
0x34b655…2a6f
10 touches
10 conflicts
0x7c68d10b…8386
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x5086c64a…28ba
0x34b655…2a6f
6 touches
3 conflicts
0xed863ec8…90d7
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
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 0x56fe17b85b…1639b1
Audit this contract →
← previous block·next block →recent activity