← previous blocknext block →recent activity
Analyzing
Block #102,358,699
24 transactions · 22 stateful · 2026-09-06 03:09:50 UTC
Parallelism
92/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,358,699 · 24 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
2w05w19w010w112w013w117w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee8defd7…73c4
0xe52b14…7230
4 touches
1 conflict
0xef7c06bc…c2eb
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xa169711f…c7f3
0x34b655…2a6f
4 touches
1 conflict
0xab3ad3dc…2a56
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09e0690d…6e3d
0xe52b14…7230
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: 0xe52b1424…bb7230
1 conflict on slot 0xee8defd72e…3d73c4
Audit this contract →
← previous block·next block →recent activity