← previous blocknext block →recent activity
Analyzing
Block #102,171,099
14 transactions · 12 stateful · 2026-09-05 11:19:18 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,171,099 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w010w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0dc2aef…ea3e
0x34b655…2a6f
4 touches
1 conflict
0xbc7d5199…c05f
0x34b655…2a6f
4 touches
1 conflict
0xc7954a60…d294
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe1af7d74…7621
0x34b655…2a6f
4 touches
1 conflict
0xe1af7d74…7622
0x34b655…2a6f
4 touches
1 conflict
0x588380ee…0a5c
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
1 conflict on slot 0xa0dc2aef0d…efea3e
Audit this contract →
← previous block·next block →recent activity