← previous blocknext block →recent activity
Analyzing
Block #83,843,884
10 transactions · 9 stateful · 2026-06-26 15:33:32 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,843,884 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f6a1e31…7de3
0x8fbe07…71b6
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xcac3298e…53c9
0x8fbe07…71b6
4 touches
1 conflict
0x5ebb19ec…ce9a
0xdde003…c9a4
4 touches
1 conflict
0xb983f9fc…9b91
0xdde003…c9a4
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
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: 0x8fbe0741…fa71b6
1 conflict on slot 0x9f6a1e312e…4b7de3
Audit this contract →
← previous block·next block →recent activity