← previous blocknext block →recent activity
Analyzing
Block #102,517,764
18 transactions · 17 stateful · 2026-09-06 16:35:52 UTC
Parallelism
89/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,517,764 · 18 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
2w03w05w06w07w18w09w112w113w015w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0xcc71d4c3…df5b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe7ad475a…0e41
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1a96e40e…73ed
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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: 0x80c74517…647210
1 conflict on slot 0x0000000000…00004f
Audit this contract →
← previous block·next block →recent activity