← previous blocknext block →recent activity
Analyzing
Block #101,993,537
23 transactions · 21 stateful · 2026-09-04 20:19:11 UTC
Parallelism
87/100
Blocked
24%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,993,537 · 23 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
1w03w14w05w16w27w08w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2aa7be4c…0f84
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x5c7b5ec0…0764
0x34b655…2a6f
6 touches
3 conflicts
0xe53bd661…5352
0x34b655…2a6f
4 touches
1 conflict
0x8d616e7c…a6a1
0x34b655…2a6f
4 touches
1 conflict
0x93aaefce…5be5
0x34b655…2a6f
4 touches
1 conflict
0xae8a7697…9685
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: Perpl
3 conflicts on slot 0x2aa7be4c59…960f84
Audit this contract →
← previous block·next block →recent activity