← previous blocknext block →recent activity
Analyzing
Block #102,481,218
20 transactions · 19 stateful · 2026-09-06 13:30:28 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,481,218 · 20 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
1w02w14w06w110w011w112w013w115w216w317w118w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18e86f02…fa98
0x34b655…2a6f
6 touches
3 conflicts
0x03a4d625…a24e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x023fcf67…6dd2
0x34b655…2a6f
6 touches
3 conflicts
0x7fd55c5f…1f35
0x34b655…2a6f
5 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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 0x18e86f023b…67fa98
Audit this contract →
← previous block·next block →recent activity