← previous blocknext block →recent activity
Analyzing
Block #102,640,041
14 transactions · 14 stateful · 2026-09-07 02:55:09 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,640,041 · 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
3w04w16w08w09w111w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbdf1d70…6c25
0x34b655…2a6f
6 touches
3 conflicts
0xb7960be3…7f19
0x34b655…2a6f
4 touches
1 conflict
0xcc976b1c…69c9
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x57070322…bc66
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x28e0a08c…8eef
0xe52b14…7230
3 touches
1 conflict
0x18860aca…0f33
0x34b655…2a6f
2 touches
0 conflicts
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 0xdbdf1d70ae…626c25
Audit this contract →
← previous block·next block →recent activity