← previous blocknext block →recent activity
Analyzing
Block #83,468,415
17 transactions · 15 stateful · 2026-06-24 21:48:20 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,468,415 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w19w211w013w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x126a0344…4465
0x34b655…2a6f
8 touches
6 conflicts
0x4d98a8ff…87f3
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x89fa3104…8020
0x34b655…2a6f
6 touches
3 conflicts
0x393dfd73…ff57
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x5d32a251…d929
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 0x126a0344b1…d04465
Audit this contract →
← previous block·next block →recent activity