← previous blocknext block →recent activity
Analyzing
Block #101,817,234
13 transactions · 9 stateful · 2026-09-04 05:28:00 UTC
Parallelism
77/100
Blocked
22%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,817,234 · 13 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
3w05w010w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68596e3e…c6e6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x41904147…5dd3
0x34b655…2a6f
2 touches
0 conflicts
0x4dffc33e…068d
0x34b655…2a6f
2 touches
0 conflicts
0x78d72c99…2878
0x34b655…2a6f
2 touches
0 conflicts
0x7daf6443…fd36
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 0x68596e3e63…14c6e6
Audit this contract →
← previous block·next block →recent activity