← previous blocknext block →recent activity
Analyzing
Block #86,056,343
22 transactions · 16 stateful · 2026-07-06 21:20:55 UTC
Parallelism
91/100
Blocked
19%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,056,343 · 22 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
1w05w06w117w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9b36f19f…fa5a
0x34b655…2a6f
4 touches
1 conflict
0xa678cb89…4abd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6ece88e2…76ec
0x065c9d…c394
3 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
2 touches
0 conflicts
0x00000000…0003
0x63e48b…53f2
2 touches
0 conflicts
0x00000000…0004
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
1 conflict on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity