← previous blocknext block →recent activity
Analyzing
Block #102,671,951
20 transactions · 13 stateful · 2026-09-07 05:35:41 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,671,951 · 20 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
7w08w09w112w013w116w117w218w319w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f5831e5…02b2
0x34b655…2a6f
6 touches
3 conflicts
0x731d7308…fd26
0x34b655…2a6f
6 touches
3 conflicts
0xa3dee461…96b8
0x34b655…2a6f
6 touches
3 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x22f10271…841d
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 0x3f5831e5e5…ee02b2
Audit this contract →
← previous block·next block →recent activity