← previous blocknext block →recent activity
Analyzing
Block #101,800,988
16 transactions · 15 stateful · 2026-09-04 04:06:18 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,800,988 · 16 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
1w02w16w07w19w010w113w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x611fe14b…aa19
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x1867b653…e61b
0x34b655…2a6f
4 touches
1 conflict
0x703951d0…178e
0x34b655…2a6f
4 touches
1 conflict
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0x89eaf36a…4e48
0x34b655…2a6f
4 touches
1 conflict
0xaa71850b…95ea
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 0x611fe14b03…3daa19
Audit this contract →
← previous block·next block →recent activity