← previous blocknext block →recent activity
Analyzing
Block #102,205,907
23 transactions · 21 stateful · 2026-09-05 14:15:41 UTC
Parallelism
87/100
Blocked
38%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,205,907 · 23 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
2w03w14w26w07w110w011w113w018w119w120w221w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd868fb65…3b4a
0xe1c8b7…3022
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5b0621ee…3c2c
0x284f45…7777
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x05e5f02e…caaf
0x34b655…2a6f
4 touches
1 conflict
0x113a6203…5dd8
0x34b655…2a6f
4 touches
1 conflict
0x6636a104…d595
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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: 0xe1c8b733…e33022
1 conflict on slot 0xd868fb65f1…2f3b4a
Audit this contract →
← previous block·next block →recent activity