← previous blocknext block →recent activity
Analyzing
Block #84,411,119
17 transactions · 13 stateful · 2026-06-29 06:33:02 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,411,119 · 17 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
1w02w14w05w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00d87b1e…ac16
0x34b655…2a6f
4 touches
1 conflict
0xbd68c7c7…40b3
0x34b655…2a6f
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x76530992…a4a7
0x5afd3e…7620
4 touches
1 conflict
0xfcfeb4f8…8696
0x5afd3e…7620
4 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0xef28bd48…e2fa
0xd32edf…ff58
3 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 0x00d87b1ecc…48ac16
Audit this contract →
← previous block·next block →recent activity