← previous blocknext block →recent activity
Analyzing
Block #101,674,002
23 transactions · 20 stateful · 2026-09-03 17:27:36 UTC
Parallelism
74/100
Blocked
45%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,674,002 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w18w210w312w413w520w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6823c28e…594c
0x34b655…2a6f
4 touches
1 conflict
0x52c63247…ce02
0x0a3323…0a3c
4 touches
1 conflict
0x477cb4f5…11b4
0x34b655…2a6f
4 touches
1 conflict
0x65f011a5…bc6e
0x34b655…2a6f
4 touches
1 conflict
0x898a08aa…c855
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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: 0xf5b5f7f8…a36d70
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity