← previous blocknext block →recent activity
Analyzing
Block #108,309,875
18 transactions · 18 stateful · 2026-09-26 23:26:24 UTC
Parallelism
61/100
Blocked
61%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,309,875 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w08w29w310w111w412w513w614w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8058ec4…ebac
0x34b655…2a6f
10 touches
10 conflicts
0x394c3833…b4a8
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x3f451a59…e324
0x34b655…2a6f
8 touches
6 conflicts
0xb840236a…70be
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0019
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 0xe8058ec456…d4ebac
Audit this contract →
← previous block·next block →recent activity