← previous blocknext block →recent activity
Analyzing
Block #84,544,839
19 transactions · 16 stateful · 2026-06-29 21:25:00 UTC
Parallelism
89/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,544,839 · 19 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
1w02w17w08w110w012w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf5ec001…5af9
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xaee73662…e759
0x40c49f…2af0
2 touches
0 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
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 0xaf5ec0013f…585af9
Audit this contract →
← previous block·next block →recent activity