← previous blocknext block →recent activity
Analyzing
Block #102,213,398
18 transactions · 18 stateful · 2026-09-05 14:53:37 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,213,398 · 18 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
7w08w110w013w114w215w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35cfc48b…9674
0x34b655…2a6f
6 touches
3 conflicts
0xca6ae23d…0a81
0x34b655…2a6f
6 touches
3 conflicts
0x1a3d2527…8ca0
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xbdccf563…1246
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…004c
0x80c745…7210
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 0x35cfc48bea…3e9674
Audit this contract →
← previous block·next block →recent activity