← previous blocknext block →recent activity
Analyzing
Block #83,903,143
10 transactions · 9 stateful · 2026-06-26 22:08:54 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,903,143 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0xa142fcce…5863
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd2cdfa3f…f071
0x34b655…2a6f
4 touches
1 conflict
0xd5a6a18c…bf80
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe22ab637…7a8e
0x34b655…2a6f
4 touches
1 conflict
0x5ba4db2b…2f04
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
1 conflict on slot 0x826cce18ca…e5251c
Audit this contract →
← previous block·next block →recent activity