← previous blocknext block →recent activity
Analyzing
Block #87,592,218
17 transactions · 13 stateful · 2026-07-14 00:28:26 UTC
Parallelism
76/100
Blocked
46%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,592,218 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w26w310w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe197e523…ef9c
0x34b655…2a6f
6 touches
3 conflicts
0xf5adc2ae…ac32
0x34b655…2a6f
4 touches
1 conflict
0xd33ebcd0…9f7e
0x34b655…2a6f
4 touches
1 conflict
0xdf39e0b5…6504
0x34b655…2a6f
4 touches
1 conflict
0xe181f491…f4e3
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
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 0xe197e52366…87ef9c
Audit this contract →
← previous block·next block →recent activity