← previous blocknext block →recent activity
Analyzing
Block #84,240,694
12 transactions · 10 stateful · 2026-06-28 11:37:22 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,240,694 · 12 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
1w02w16w17w210w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb87
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x6f58168d48…e3ea24
Audit this contract →
← previous block·next block →recent activity