← previous blocknext block →recent activity
Analyzing
Block #85,248,570
15 transactions · 15 stateful · 2026-07-03 03:38:01 UTC
Parallelism
87/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,248,570 · 15 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
1w02w110w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c98b7be…dc4e
0x34b655…2a6f
4 touches
1 conflict
0x9cf2d0bf…8d46
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2697123c…8526
0x34b655…2a6f
4 touches
1 conflict
0x07edc7b1…9cdf
0x40c49f…2af0
2 touches
0 conflicts
0x2934e250…4561
0x40c49f…2af0
2 touches
0 conflicts
0x7de51d54…948f
0x40c49f…2af0
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 0x3c98b7be24…cfdc4e
Audit this contract →
← previous block·next block →recent activity