← previous blocknext block →recent activity
Analyzing
Block #83,667,020
17 transactions · 16 stateful · 2026-06-25 19:53:23 UTC
Parallelism
47/100
Blocked
63%
Avg conflicts / tx
2.24
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,667,020 · 17 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w49w510w611w712w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xaa7ee7…f0e4
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c3
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
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: 0xaa7ee7ce…aff0e4
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity