← previous blocknext block →recent activity
Analyzing
Block #86,316,139
15 transactions · 13 stateful · 2026-07-08 02:15:11 UTC
Parallelism
87/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,316,139 · 15 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
1w06w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3581dd00…56e6
0x065c9d…c394
2 touches
0 conflicts
0x3aa2ee9b…8c34
0x065c9d…c394
2 touches
0 conflicts
0x3ea110a4…436d
0x065c9d…c394
2 touches
0 conflicts
0x67060d54…8edd
0x065c9d…c394
2 touches
0 conflicts
0xae6073c8…245f
0x065c9d…c394
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: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity