← previous blocknext block →recent activity
Analyzing
Block #101,816,911
19 transactions · 17 stateful · 2026-09-04 05:26:23 UTC
Parallelism
89/100
Blocked
29%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,816,911 · 19 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
1w02w03w14w05w17w08w112w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x433eee0a…5453
0x34b655…2a6f
4 touches
1 conflict
0x4dffc33e…068d
0x34b655…2a6f
4 touches
1 conflict
0x68596e3e…c6e6
0x34b655…2a6f
4 touches
1 conflict
0x7daf6443…fd36
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x987859be…2686
0x34b655…2a6f
4 touches
1 conflict
0xd60f85f5…d01d
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
1 conflict on slot 0x3d13406e14…e9eff1
Audit this contract →
← previous block·next block →recent activity