← previous blocknext block →recent activity
Analyzing
Block #102,098,631
26 transactions · 24 stateful · 2026-09-05 05:11:52 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,098,631 · 26 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
4w06w07w19w211w016w017w118w219w320w421w122w423w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cecfed5…f339
0x34b655…2a6f
8 touches
6 conflicts
0xfc24540b…6463
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xe82e5e3d…a872
0x34b655…2a6f
7 touches
6 conflicts
0x9cf9008a…d826
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
6 touches
3 conflicts
0x71b395d9…1697
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x8cecfed594…c1f339
Audit this contract →
← previous block·next block →recent activity