← previous blocknext block →recent activity
Analyzing
Block #102,155,608
15 transactions · 14 stateful · 2026-09-05 10:00:42 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,155,608 · 15 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
2w03w14w05w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfef0ce0a…aa7f
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xdc7b9eda…e616
0x34b655…2a6f
4 touches
1 conflict
0xec9030a2…0020
0x34b655…2a6f
4 touches
1 conflict
0xf1894e7f…30fe
0x34b655…2a6f
4 touches
1 conflict
0x2e37bcee…5415
0x34b655…2a6f
4 touches
1 conflict
0x328303dd…744f
0x34b655…2a6f
4 touches
1 conflict
0x56a284d9…32e4
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 0xfef0ce0aa8…efaa7f
Audit this contract →
← previous block·next block →recent activity