← previous blocknext block →recent activity
Analyzing
Block #100,730,919
10 transactions · 9 stateful · 2026-08-31 10:22:15 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,730,919 · 10 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
1w02w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf275b4ca…57b8
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x73141abe…2fbc
0xe52b14…7230
3 touches
1 conflict
0x47e2a668…be99
0x34b655…2a6f
2 touches
0 conflicts
0x76e2c80e…1811
0x34b655…2a6f
2 touches
0 conflicts
0xac206e47…ef7d
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: Kuru Exchange: MarginAccount
1 conflict on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity