← previous blocknext block →recent activity
Analyzing
Block #85,907,307
13 transactions · 11 stateful · 2026-07-06 04:46:04 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,907,307 · 13 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
1w05w16w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0x397501e2…9a12
0x34b655…2a6f
4 touches
1 conflict
0xcc25f1e5…2cac
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x3dbd9177…e936
0xea1b8e…c5ec
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0xa8abcc19…3d83
0xea1b8e…c5ec
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 0x1aaf499609…4665ec
Audit this contract →
← previous block·next block →recent activity