← previous blocknext block →recent activity
Analyzing
Block #101,971,522
12 transactions · 12 stateful · 2026-09-04 18:27:26 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,971,522 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w010w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x1f4e6c86…7789
0x34b655…2a6f
2 touches
0 conflicts
0x66fdc53a…e217
0x34b655…2a6f
2 touches
0 conflicts
0x74ba5890…79bc
0x34b655…2a6f
2 touches
0 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
2 touches
0 conflicts
0xdd7386fd…1dba
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity