← previous blocknext block →recent activity
Analyzing
Block #83,656,066
16 transactions · 14 stateful · 2026-06-25 18:40:21 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,656,066 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w310w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c53a187…3646
0x34b655…2a6f
8 touches
6 conflicts
0xa1d40792…40d9
0x34b655…2a6f
6 touches
3 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
6 touches
3 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5f3fc680…f989
0x34b655…2a6f
6 touches
3 conflicts
0x5eeea918…8147
0x34b655…2a6f
4 touches
1 conflict
0x73ca2093…8dd6
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
6 conflicts on slot 0x2c53a187ea…bc3646
Audit this contract →
← previous block·next block →recent activity