← previous blocknext block →recent activity
Analyzing
Block #83,903,464
33 transactions · 29 stateful · 2026-06-26 22:11:03 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,903,464 · 33 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
1w02w03w14w25w36w47w012w018w019w123w124w125w028w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0x655939a8…0b3b
0x336ed4…c59c
10 touches
10 conflicts
0x659bf1d4…2024
0x336ed4…c59c
10 touches
10 conflicts
0xfc111d09…525a
0x336ed4…c59c
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xd98b3c10…67b8
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: 0x90c3747c…0ebe45
10 conflicts on slot 0x0000000000…00000b
Audit this contract →
← previous block·next block →recent activity