← previous blocknext block →recent activity
Analyzing
Block #84,075,541
19 transactions · 14 stateful · 2026-06-27 17:17:16 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,075,541 · 19 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
1w012w113w114w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0xba909c61…cb99
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x98b3e54a…913f
0xa6afd3…d132
3 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
2 touches
0 conflicts
0x00000000…0004
0x63e48b…53f2
2 touches
0 conflicts
0x00000000…0077
0x63e48b…53f2
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
3 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity