← previous blocknext block →recent activity
Analyzing
Block #86,157,104
19 transactions · 16 stateful · 2026-07-07 08:33:18 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,157,104 · 19 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
2w03w16w07w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a7fb5b5…f0e5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x517d35c7…f359
0x34b655…2a6f
4 touches
1 conflict
0x4d658fb7…ed44
0x34b655…2a6f
2 touches
0 conflicts
0x515845c6…0729
0x34b655…2a6f
2 touches
0 conflicts
0x62fa338b…9140
0x34b655…2a6f
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 0x3a7fb5b5df…c1f0e5
Audit this contract →
← previous block·next block →recent activity