← previous blocknext block →recent activity
Analyzing
Block #101,491,209
19 transactions · 16 stateful · 2026-09-03 02:08:01 UTC
Parallelism
84/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,491,209 · 19 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c7c1a4b…5751
0x34b655…2a6f
4 touches
1 conflict
0x6cda5bc9…8e0e
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xa62eb46f…89b1
0x34b655…2a6f
4 touches
1 conflict
0xc03a14df…a863
0x34b655…2a6f
4 touches
1 conflict
0xffd04294…cf0e
0x34b655…2a6f
4 touches
1 conflict
0x2249932e…474a
0x34b655…2a6f
2 touches
0 conflicts
0x26eb478a…0088
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 0x6c7c1a4b7d…d35751
Audit this contract →
← previous block·next block →recent activity