← previous blocknext block →recent activity
Analyzing
Block #85,172,347
20 transactions · 18 stateful · 2026-07-02 19:10:15 UTC
Parallelism
90/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,172,347 · 20 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
1w03w010w117w018w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x557c6f05…51c4
0x5afd3e…7620
4 touches
1 conflict
0x57bc95a7…d18d
0x5afd3e…7620
4 touches
1 conflict
0xc088072f…d57b
0x5afd3e…7620
4 touches
1 conflict
0xd86435c2…fd3b
0x5afd3e…7620
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0006
0x8b0d32…7367
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: Perpl
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity