← previous blocknext block →recent activity
Analyzing
Block #87,078,102
16 transactions · 14 stateful · 2026-07-11 15:09:14 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,078,102 · 16 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
1w02w17w08w09w110w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf10e1bf…0391
0x34b655…2a6f
6 touches
3 conflicts
0x1048df8e…4c9f
0x34b655…2a6f
4 touches
1 conflict
0x31519d10…f76b
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
0x44d24653…fa2f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x63ef3eae…b1ea
0x34b655…2a6f
4 touches
1 conflict
0x705b60c4…a494
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xaf10e1bfee…b50391
Audit this contract →
← previous block·next block →recent activity