← previous blocknext block →recent activity
Analyzing
Block #101,799,940
13 transactions · 13 stateful · 2026-09-04 04:01:01 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,799,940 · 13 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
3w04w05w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e20f690…e1d8
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0f43bfc7…1de5
0x34b655…2a6f
4 touches
1 conflict
0xc6615a36…3cf0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x66f12d1d…d17f
0x34b655…2a6f
2 touches
0 conflicts
0x945abafb…c3a1
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 0x7e20f690e7…cae1d8
Audit this contract →
← previous block·next block →recent activity