← previous blocknext block →recent activity
Analyzing
Block #86,350,888
15 transactions · 14 stateful · 2026-07-08 06:07:13 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,350,888 · 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
2w03w16w07w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d537073…cf27
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x060aae4e…f1d0
0x34b655…2a6f
4 touches
1 conflict
0x0ecec63a…4a94
0x065c9d…c394
2 touches
0 conflicts
0x2d62c9c6…c7f8
0x065c9d…c394
2 touches
0 conflicts
0x3ea110a4…436d
0x065c9d…c394
2 touches
0 conflicts
0x824eb04f…8756
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: Perpl
1 conflict on slot 0x5d537073f1…d2cf27
Audit this contract →
← previous block·next block →recent activity