← previous blocknext block →recent activity
Analyzing
Block #101,018,314
15 transactions · 12 stateful · 2026-09-01 10:28:24 UTC
Parallelism
73/100
Blocked
42%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,018,314 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w17w29w312w013w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0003
0xf5b5f7…6d70
4 touches
1 conflict
0x2fad1943…3586
0x754704…b603
4 touches
1 conflict
0x69c8bf4a…2ed0
0x754704…b603
4 touches
1 conflict
0x00000000…0007
0xc35b1c…298f
4 touches
1 conflict
0x00000000…000a
0xc35b1c…298f
4 touches
1 conflict
0x81955a0a…29ee
0xc9d9fa…20f2
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity