← previous blocknext block →recent activity
Analyzing
Block #101,062,894
28 transactions · 26 stateful · 2026-09-01 14:12:42 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,062,894 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w18w19w210w316w118w219w124w225w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23529e13…6f25
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x065ff70b…356d
0x40c49f…2af0
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x4f133478…22ca
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
6 conflicts on slot 0x23529e136b…8a6f25
Audit this contract →
← previous block·next block →recent activity