← previous blocknext block →recent activity
Analyzing
Block #101,798,694
14 transactions · 12 stateful · 2026-09-04 03:54:45 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,798,694 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w011w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30f7b5bf…14c6
0x34b655…2a6f
6 touches
3 conflicts
0xe8f860c0…35c9
0x34b655…2a6f
4 touches
1 conflict
0x9b4f173c…94e6
0x34b655…2a6f
4 touches
1 conflict
0xb3e293fe…be2e
0x34b655…2a6f
4 touches
1 conflict
0xb826ef15…d248
0x34b655…2a6f
4 touches
1 conflict
0xbc4f45e2…2117
0x34b655…2a6f
4 touches
1 conflict
0xc37e3093…d769
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
3 conflicts on slot 0x30f7b5bf4d…4914c6
Audit this contract →
← previous block·next block →recent activity