← previous blocknext block →recent activity
Analyzing
Block #83,653,943
13 transactions · 12 stateful · 2026-06-25 18:26:15 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,653,943 · 13 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
1w02w03w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bd818fc…4f86
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
0x34b655…2a6f
2 touches
0 conflicts
0x5d7f309d…5145
0x34b655…2a6f
2 touches
0 conflicts
0x6a0d9e84…2b0b
0x34b655…2a6f
2 touches
0 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
2 touches
0 conflicts
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 0x5bd818fcf8…714f86
Audit this contract →
← previous block·next block →recent activity