← previous blocknext block →recent activity
Analyzing
Block #87,410,437
16 transactions · 14 stateful · 2026-07-13 04:12:01 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,410,437 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w09w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ccf5c86…9954
0x851145…3f07
6 touches
3 conflicts
0x9e49f754…23a2
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0cd025f3…a36e
0x34b655…2a6f
4 touches
1 conflict
0x3f4d9d89…7299
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: 0x851145ea…9f3f07
3 conflicts on slot 0x6ccf5c865d…b29954
Audit this contract →
← previous block·next block →recent activity