← previous blocknext block →recent activity
Analyzing
Block #84,360,103
13 transactions · 12 stateful · 2026-06-29 00:53:02 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,360,103 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w08w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9966da31…0d0f
0x34b655…2a6f
4 touches
1 conflict
0x277c8112…6b07
0x40c49f…2af0
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x617629c3…3907
0x34b655…2a6f
2 touches
0 conflicts
0x75194ada…a1c5
0x34b655…2a6f
2 touches
0 conflicts
0x75291f8b…3ac0
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 0x9966da3102…c80d0f
Audit this contract →
← previous block·next block →recent activity