← previous blocknext block →recent activity
Analyzing
Block #84,024,308
16 transactions · 14 stateful · 2026-06-27 11:36:06 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,024,308 · 16 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
1w02w16w07w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb99958f6…ccf0
0x34b655…2a6f
4 touches
1 conflict
0xb99958f6…ccf1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2484cc15…5afc
0x34b655…2a6f
4 touches
1 conflict
0x3cf50d44…961b
0x34b655…2a6f
4 touches
1 conflict
0x46fc15ad…349e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
1 conflict on slot 0xb99958f6c8…c6ccf0
Audit this contract →
← previous block·next block →recent activity