← previous blocknext block →recent activity
Analyzing
Block #102,518,839
23 transactions · 18 stateful · 2026-09-06 16:41:20 UTC
Parallelism
91/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,518,839 · 23 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
4w07w08w114w015w116w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0005a008…264a
0x34b655…2a6f
4 touches
1 conflict
0x1a409a89…2e84
0x34b655…2a6f
4 touches
1 conflict
0x4635fb46…4cfd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x581b829b…9578
0x34b655…2a6f
4 touches
1 conflict
0x71892c70…660d
0x34b655…2a6f
4 touches
1 conflict
0x754bbcbe…427e
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
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 0x0005a008c4…88264a
Audit this contract →
← previous block·next block →recent activity