← previous blocknext block →recent activity
Analyzing
Block #100,617,469
22 transactions · 19 stateful · 2026-08-31 00:51:34 UTC
Parallelism
77/100
Blocked
37%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,617,469 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w113w015w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x00000000…0050
0x80c745…7210
4 touches
1 conflict
0x08e6e52f…3d80
0x34b655…2a6f
4 touches
1 conflict
0xf52df78b…16a0
0x851145…3f07
4 touches
1 conflict
0x8db32935…81a7
0x34b655…2a6f
4 touches
1 conflict
0x8b87ece6…3353
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity