← previous blocknext block →recent activity
Analyzing
Block #101,817,982
9 transactions · 9 stateful · 2026-09-04 05:31:46 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,817,982 · 9 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
1w02w13w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0x12e77486…ec2b
0x34b655…2a6f
2 touches
0 conflicts
0x1fb8364c…c10d
0x34b655…2a6f
2 touches
0 conflicts
0x34dad526…5f98
0x34b655…2a6f
2 touches
0 conflicts
0x3c9b10c1…d791
0x34b655…2a6f
2 touches
0 conflicts
0x6d5d1fb5…86a7
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity