← previous blocknext block →recent activity
Analyzing
Block #102,214,900
18 transactions · 16 stateful · 2026-09-05 15:01:12 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,214,900 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w17w210w311w413w514w615w717w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x487bd835…8723
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x20b94f7c…2a9b
0x34b655…2a6f
8 touches
6 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
6 touches
3 conflicts
0xca608d0c…f23b
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd02ebff8…fe31
0x34b655…2a6f
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
15 conflicts on slot 0x487bd83556…af8723
Audit this contract →
← previous block·next block →recent activity