← previous blocknext block →recent activity
Analyzing
Block #86,224,878
15 transactions · 15 stateful · 2026-07-07 16:05:48 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,224,878 · 15 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
1w02w03w14w05w09w110w213w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1d76dba…4de3
0x34b655…2a6f
4 touches
1 conflict
0xc4088775…0731
0x065c9d…c394
4 touches
1 conflict
0x1d290f8b…2ad7
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0xd29e547b…a1dd
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
1 conflict on slot 0xf1d76dbab2…f04de3
Audit this contract →
← previous block·next block →recent activity