← previous blocknext block →recent activity
Analyzing
Block #83,875,914
16 transactions · 16 stateful · 2026-06-26 19:07:14 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,875,914 · 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
1w02w04w15w26w37w18w211w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e45419…f17b
0x34b655…2a6f
6 touches
3 conflicts
0xe0532746…0224
0x851145…3f07
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb80
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
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 0xe2e454194e…59f17b
Audit this contract →
← previous block·next block →recent activity