← previous blocknext block →recent activity
Analyzing
Block #101,025,736
21 transactions · 19 stateful · 2026-09-01 11:05:46 UTC
Parallelism
76/100
Blocked
32%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,025,736 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w08w19w010w113w214w316w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfaa9666…2003
0x34b655…2a6f
6 touches
3 conflicts
0xe26c4e53…94c3
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xe26c4e53…94c2
0x34b655…2a6f
4 touches
1 conflict
0x33b5035a…d1c6
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 0xdfaa9666ca…322003
Audit this contract →
← previous block·next block →recent activity