← previous blocknext block →recent activity
Analyzing
Block #84,195,347
7 transactions · 7 stateful · 2026-06-28 06:35:00 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,195,347 · 7 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8372997…869e
0x34b655…2a6f
4 touches
1 conflict
0x77674e3c…0f43
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8a01f41e…d4bf
0x34b655…2a6f
3 touches
1 conflict
0x969f2d28…4fa2
0x0555e3…2b9c
2 touches
0 conflicts
0x9a69fe57…7e9f
0x0555e3…2b9c
2 touches
0 conflicts
0xa590e52f…fdfd
0x0555e3…2b9c
2 touches
0 conflicts
0x60f24ede…d2b1
0x065c9d…c394
2 touches
0 conflicts
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 0xf8372997e5…13869e
Audit this contract →
← previous block·next block →recent activity