← previous blocknext block →recent activity
Analyzing
Block #84,177,098
14 transactions · 14 stateful · 2026-06-28 04:33:33 UTC
Parallelism
79/100
Blocked
14%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,177,098 · 14 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
11w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cc8dd43…8cf2
0x34b655…2a6f
6 touches
3 conflicts
0x610aa855…5ecd
0x34b655…2a6f
6 touches
3 conflicts
0x9ac79c76…c4a9
0x34b655…2a6f
6 touches
3 conflicts
0x1a1ff3c7…bc09
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x73db5c19…dee8
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x7e17e82a…9748
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
3 conflicts on slot 0x5cc8dd430f…428cf2
Audit this contract →
← previous block·next block →recent activity