← previous blocknext block →recent activity
Analyzing
Block #84,075,044
10 transactions · 7 stateful · 2026-06-27 17:13:57 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,075,044 · 10 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
4w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0xd16df6cd…5532
0x40c49f…2af0
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0xcd9a9bc6…b25f
0x065c9d…c394
2 touches
0 conflicts
0xfb41a7f4…bbb8
0x065c9d…c394
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
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: Kuru Exchange: MarginAccount
1 conflict on slot 0x5581d709b4…95ab77
Audit this contract →
← previous block·next block →recent activity