← previous blocknext block →recent activity
Analyzing
Block #84,137,163
18 transactions · 14 stateful · 2026-06-28 00:07:53 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,137,163 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w011w112w215w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfca3cd0…5023
0x34b655…2a6f
6 touches
3 conflicts
0xb2cdadc7…d414
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x4e7eb462…b2af
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
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 0xbfca3cd067…cd5023
Audit this contract →
← previous block·next block →recent activity