← previous blocknext block →recent activity
Analyzing
Block #101,991,928
65 transactions · 64 stateful · 2026-09-04 20:11:03 UTC
Parallelism
95/100
Blocked
5%
Avg conflicts / tx
0.06
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,991,928 · 65 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
2w03w16w063w164w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdcaadcf…1c9f
0x34b655…2a6f
4 touches
1 conflict
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xddc5beb2…3f56
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x2dfc834d…12be
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
1 conflict on slot 0xcdcaadcfae…c11c9f
Audit this contract →
← previous block·next block →recent activity