← previous blocknext block →recent activity
Analyzing
Block #101,803,095
15 transactions · 13 stateful · 2026-09-04 04:16:53 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,803,095 · 15 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
2w04w05w06w18w19w213w014w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed506426…e6ad
0x34b655…2a6f
6 touches
3 conflicts
0xdc90bed5…58a9
0x34b655…2a6f
4 touches
1 conflict
0x3ae7b171…b69f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x312abbb3…0237
0x34b655…2a6f
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x74e46435…fdcd
0x34b655…2a6f
4 touches
1 conflict
0xb0e974c4…b84d
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 0xed506426bf…a1e6ad
Audit this contract →
← previous block·next block →recent activity