← previous blocknext block →recent activity
Analyzing
Block #102,408,747
26 transactions · 25 stateful · 2026-09-06 07:23:19 UTC
Parallelism
85/100
Blocked
28%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,408,747 · 26 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
1w03w04w16w08w110w112w113w214w317w021w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x165c0eeb…95d1
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
0x34b655…2a6f
4 touches
1 conflict
0xf5893393…464c
0x34b655…2a6f
4 touches
1 conflict
0xab8bc634…5e45
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
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 0x165c0eeb5d…4395d1
Audit this contract →
← previous block·next block →recent activity